On Mon, Aug 28, 2017 at 5:21 PM Reid Kleckner wrote:
> On Mon, Aug 28, 2017 at 5:02 PM, David Blaikie wrote:
>
>> Feels like this alignment attribute may be a bit of a death trap, then?
>> Should other uses of the attribute be scrutinized, or could we come up with
>> a portable way to use it saf
On Mon, Aug 28, 2017 at 5:02 PM, David Blaikie wrote:
> Feels like this alignment attribute may be a bit of a death trap, then?
> Should other uses of the attribute be scrutinized, or could we come up with
> a portable way to use it safely? (using a different attribute on different
> compilers -
Feels like this alignment attribute may be a bit of a death trap, then?
Should other uses of the attribute be scrutinized, or could we come up with
a portable way to use it safely? (using a different attribute on different
compilers - sounded like maybe one form worked with MSVC and a different
for
Author: rnk
Date: Mon Aug 14 18:17:47 2017
New Revision: 310905
URL: http://llvm.org/viewvc/llvm-project?rev=310905&view=rev
Log:
Avoid PointerIntPair of constexpr EvalInfo structs
They are stack allocated, so their alignment is not to be trusted.
32-bit MSVC only guarantees 4 byte stack alignmen
