| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to take type alignment padding into account whe computing physical
layouts.
The layout must be compatible with the input layout, offsets are defined in
terms of offsets within a packed struct which are computed in terms of the alloc
size of a type.
Usingthe store size we would insert padding for the following type for example:
struct {
int3 v;
long long l;
} __attribute((packed))
On x86-64 int3 is padded to int4 alignment. The swiftcc type would be
<{ <3 x float>, [4 x i8], i64 }> which is not compatible with <{ <3 x float>,
i64 }>.
The latter has i64 at offset 16 and the former at offset 20.
rdar://32618125
llvm-svn: 305956
|
| |
|
|
|
|
| |
rdar://32401301
llvm-svn: 304017
|
| |
|
|
|
|
|
|
|
|
|
| |
windows bots"
This reverts commit r284174. The tests pass for me locally. It must have
been a 2015 only crash.
Fixes PR30699
llvm-svn: 284781
|
| |
|
|
| |
llvm-svn: 284285
|
| |
|
|
|
|
|
|
|
|
|
| |
The backtrace on the bot does not give me any indication what is wrong.
The test case interestingly passes in stage2 of the build.
I don't have a way of debugging this.
Disable the test on windows and hope if there is truly a bug in the code that
was causing we will eventually run into this on other platforms.
llvm-svn: 284174
|
| |
|
|
| |
llvm-svn: 284162
|
| |
|
|
|
|
|
|
|
|
| |
Use iterator instead of address of element in vector
It is not valid to access one after the last element.
rdar://28759508
llvm-svn: 284150
|
|
|
llvm-svn: 284133
|
