Duncan Sands 5a6c6a92c1 Change packed struct layout so that field sizes ... are the same as in unpacked structs, only field positions differ. This only matters for structs containing x86 long double or an apint; it may cause backwards compatibility problems if someone has bitcode containing a packed struct with a field of one of those types. The issue is that only 10 bytes are needed to hold an x86 long double: the store size is 10 bytes, but the ABI size is 12 or 16 bytes (linux/ darwin) which comes from rounding the store size up by the alignment. Because it seemed silly not to pack an x86 long double into 10 bytes in a packed struct, this is what was done. I now think this was a mistake. Reserving the ABI size for an x86 long double field even in a packed struct makes things more uniform: the ABI size is now always used when reserving space for a type. This means that developers are less likely to make mistakes. It also makes life easier for the CBE which otherwise could not represent all LLVM packed structs (PR2402). Front-end people might need to adjust the way they create LLVM structs - see following change to llvm-gcc. llvm-svn: 51928		2008-06-04 08:21:45 +00:00
..
Hello	Clean up the use of static and anonymous namespaces. This turned up	2008-05-13 00:00:25 +00:00
Instrumentation	Tidy up BasicBlock::getFirstNonPHI, and change a bunch of places to	2008-05-23 21:05:58 +00:00
IPO	Use eraseFromParent() instead of doing that manually in two places.	2008-05-30 12:35:46 +00:00
Scalar	Change packed struct layout so that field sizes	2008-06-04 08:21:45 +00:00
Utils	LoopIndexSplit can sometimes result in cases where a block in its own domfrontier.	2008-06-03 18:29:48 +00:00
Makefile	remove attribution from lib Makefiles.	2007-12-29 20:09:26 +00:00