search for: gettypepaddedsize

Displaying 5 results from an estimated 5 matches for "gettypepaddedsize".

2009 Sep 22
3
[LLVMdev] StructLayout
How are bitfields handled in StructLayout? In LLVM 2.5 the struct is unambiguously size by: StructSize += TD.getTypePaddedSize(Ty); // Consume space for this data In LLVM 2.6 it's getTypeAllocSize, which does the same thing. Unfortunately, this is not correct for bitfields. For example, LLVM reports this struct: typedef struct test1 { short f0 : 10; char f1 : 5; long f2 : 1; long f3 : 45; } test1_t; which...
2009 Mar 02
0
[LLVMdev] Please review the 2.5 release notes
...urn type was i32 and the parameter types were (i8*, i8*), but now it means something different (probably that the return type is {i32, i8*, i8*}, but I'm not sure). - BinaryOperator::createAnd -> CreateAnd (and similarly for lots of other createX functions) - TargetData::getABITypeSize -> getTypePaddedSize - APFloat::convertToAPInt -> bitcastToAPInt I don't know if any of these count as "major". Thanks, Jay.
2009 Mar 02
6
[LLVMdev] Please review the 2.5 release notes
Hi All, Please review the 2.5 release notes here: http://llvm.org/docs/ReleaseNotes.html Let me know if you have any additions, improvements, or see any oversights. If you have commit access, please just directly change the document. The release is planned to go out in about 24 hours from now! Thanks! -Chris
2009 Sep 23
0
[LLVMdev] StructLayout
...size of long is 8 on your x64 platform. Because the size of long is so different on different platform, sad it is. 2009/9/23, David Greene <dag at cray.com>: > How are bitfields handled in StructLayout? In LLVM 2.5 the > struct is unambiguously size by: > > StructSize += TD.getTypePaddedSize(Ty); // Consume space for this data > > In LLVM 2.6 it's getTypeAllocSize, which does the same thing. > > Unfortunately, this is not correct for bitfields. For example, > LLVM reports this struct: > > typedef struct test1 { > short f0 : 10; > char f1 : 5; > l...
2009 Feb 19
2
[LLVMdev] please review this fix for PR3510
Please review this patch for PR3510 (and <rdar://problem/6564697>). The bug is a failure to handle a "hole" inside an initialized structure, where the hole may be induced by a designated initializer or by alignment: http://llvm.org/bugs/show_bug.cgi?id=3510 The original code was greatly simplified by using FieldNo to index the LLVM fields and the initializer in