llvm-svn: 52089

This fix just makes sure to construct the global with the appropriate 
type, and fixes up the one user this affects to compensate.

llvm-svn: 52084

reported on cfe-dev by Cédric Venet.

Note that I seriously doubt that this perticular construct is useful, 
though: it's a pointer in an alternate address space pointing into 
unqualified address space.

llvm-svn: 52076

llvm-svn: 52070

PR2419.

llvm-svn: 52060

llvm-svn: 52049

llvm-svn: 51993

because trying to access non-existent ParamVarDecls can crash. 
Testcase from the original source for PR2414.

llvm-svn: 51960

llvm-svn: 51958

(http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080602/063306.html).

llvm-svn: 51944

llvm-svn: 51847

Patch by David Chisnall.

llvm-svn: 51840

much closer to passing the gcc struct layout tests.

It might be possible to refactor this a bit, but I'm not sure there's 
actually enough common code for that to be useful.

To get the calling convention completely correct, a bit of 
platform-specific code is necessary even for x86-Linux. On x86-Linux, the
alignment of function parameters is extremely strange; as far as I can tell,
it's always 4 except for SSE vectors or structs containing SSE vectors.  I'm 
continuing to investigate this.

llvm-svn: 51839

llvm-svn: 51838

llvm-svn: 51837

llvm-svn: 51836

Implemented by David Chisnall!

llvm-svn: 51835

llvm-svn: 51826

types so that they end up the correct size.

llvm-svn: 51787

this does is reconstruct the type for structs and arrays if the type 
wouldn't be compatible otherwise.

The assertion about packing in the struct type reconstruction code 
sucks, but I don't see any obvious way to fix it.  Maybe we need a general
utility method to take a list of types and alignments and try to construct an
unpacked type if possible?

llvm-svn: 51785

associated declaration. This is a prerequisite to handling
general union initializations; for example, an array of unions involving 
pointers has to be turned into a struct because the elements can have 
incompatible types.

I refactored the code a bit to make it more readable; now, the logic for 
definitions is all in EmitGlobalVarInit.

The second parameter for GetAddrOfGlobalVar is now dead; I'll remove it 
separately.

By itself, this patch should not cause any visible changes.

llvm-svn: 51783

of elements.

llvm-svn: 51769

This fixes a crash on the included testcase (found in NetHack).

llvm-svn: 51767

llvm-svn: 51765

llvm-svn: 51764

bit-field initialization; ugly code, X86-only, but it works, at least 
for basic stuff.  Separates/adds union initialization; currently disabled,
though, because the struct/array code needs modifications to support 
elements of the wrong type.

Fixes PR2381 and PR2309 with the bit-field initialization.  And NetHack 
compiles and appears to work with a few tweaks (to work around the lack 
of transparent_union support, and clang being a bit strict about
conflicting declarations).

llvm-svn: 51763

- #include ExprObjC.h in many places

llvm-svn: 51703

constant expressions.

llvm-svn: 51682

unsigned because it's possible (at least in theory) to have
have both positive and negative pointers pointing to the same object.

llvm-svn: 51681

in unions (we don't want to do the union-specific bitcast for 
bit-fields).

llvm-svn: 51678

expressions.

llvm-svn: 51677

alignment and alignment attributes.

llvm-svn: 51676

emit incomplete types, because they crash llc, and always use the 
logical location as the current location so we don't crash doing invalid 
queries on CurLoc.

llvm-svn: 51675

This change makes clang generate the same thing as llvm-gcc.

llvm-svn: 51674

nothing fundamentally wrong with it. Emitting unpacked structs where 
possible is more work for almost no practical benefit.  We'll probably 
want to fix it at some point anyway, but it's low priority.

The issue with long double in particular is that LLVM thinks an X86 long
double is 10 bytes, while clang considers it for all purposes to be
either 12 or 16 bytes, depending on the platform, even in a packed
struct.

llvm-svn: 51673

llvm-svn: 51619

llvm-svn: 51596

llvm-svn: 51595

llvm-svn: 51587

been used.  In preparation for the fix to PR2360, but also a minor bug 
in its own right.

llvm-svn: 51583