search for: getabitypesizeinbit

...int types. Here (1), (2) >>> and (3) are presumably 80 bits. On my machine (5) is 96 bits. >>> I'm not sure what (4) is, presumably 80 or 96. >>> >>> Which (if any) of these should getTypeSize, getABITypeSize, >>> getTypeSizeInBits >>> and getABITypeSizeInBits correspond to? >> >> TypeSize == "real size", ABITypeSize == "abi size". You will need >> another pair for the storage size? > > What is "real size"? Do you mean getTypeSizeInBits rounded up to a > multiple of 8? That was my first thought...

...-bit floating point types. Here (1), (2) > > and (3) are presumably 80 bits. On my machine (5) is 96 bits. > > I'm not sure what (4) is, presumably 80 or 96. > > > > Which (if any) of these should getTypeSize, getABITypeSize, > > getTypeSizeInBits > > and getABITypeSizeInBits correspond to? > > TypeSize == "real size", ABITypeSize == "abi size". You will need > another pair for the storage size? What is "real size"? Do you mean getTypeSizeInBits rounded up to a multiple of 8? That was my first thought too, but I came to the...

...he impression that the type comparison can be done by a pointer comparison. Can anyone please suggest me a better way to do it? Also, I want to get the size of %struct.S, should I use the following code? const TargetData &TD = getAnalysis<TargetData>(); unsigned StructSize = TD.getABITypeSizeInBits(ai->getOperand(0)->getType()); Thanks a lot. Lu

Hi Evan, > I think rather than worrying about how these functions are being used > *now* you should define them in a way that's clear and fix the > incorrect uses. To me that means: > > getTypeSizeInBits - actual size > getABITypeSizeInBits - ABI size when used in a larger structure > getStorageTypeSizeInBits - size of load / store I agree and will try to do something later this week. Ciao, Duncan. PS: getStorageTypeSizeInBits -> getTypeStorageSizeInBits

...5) needs to be at least as big as (4). Another example is 80-bit floating point types. Here (1), (2) and (3) are presumably 80 bits. On my machine (5) is 96 bits. I'm not sure what (4) is, presumably 80 or 96. Which (if any) of these should getTypeSize, getABITypeSize, getTypeSizeInBits and getABITypeSizeInBits correspond to? It seems clear that getTypeSizeInBits corresponds to (1) and (2), as shown by it returning 36 for i36. This is like gcc's TYPE_PRECISION, and is a useful concept - but I think the name should be changed, since right now it implicitly suggests it returns 8*getTypeSize. If no o...

...gt; > Another example is 80-bit floating point types. Here (1), (2) > and (3) are presumably 80 bits. On my machine (5) is 96 bits. > I'm not sure what (4) is, presumably 80 or 96. > > Which (if any) of these should getTypeSize, getABITypeSize, > getTypeSizeInBits > and getABITypeSizeInBits correspond to? TypeSize == "real size", ABITypeSize == "abi size". You will need another pair for the storage size? > > It seems clear that getTypeSizeInBits corresponds to (1) and (2), as > shown by it returning 36 for i36. This is like gcc's TYPE_PRECISION,...

...nsion__ ({ const tree __t = (Tr); if (tree_code_type[(int) (((enum tree_code) (__t)->common.code))] != (tcc_type)) tree_class_check_failed (__t, (tcc_type), "/home/chandlerc/code/compilers/llvm-gcc/gcc/llvm-types.cpp", 81, __FUNCTION__); __t; })->type.size), true) == getTargetData().getABITypeSizeInBits(Ty)) && "LLVM type size doesn't match GCC type size!"' failed. /home/chandlerc/code/compilers/llvm-gcc/gcc/libgcc2.c: In function '__powixf2': /home/chandlerc/code/compilers/llvm-gcc/gcc/libgcc2.c:1765: internal compiler error: Aborted My configure: .../configure...

...nsion__ ({ const tree __t = (Tr); if (tree_code_type[(int) (((enum tree_code) (__t)->common.code))] != (tcc_type)) tree_class_check_failed (__t, (tcc_type), "/home/chandlerc/code/compilers/llvm-gcc/gcc/llvm-types.cpp", 81, __FUNCTION__); __t; })->type.size), true) == getTargetData().getABITypeSizeInBits(Ty)) && "LLVM type size doesn't match GCC type size!"' failed. testcase.i: In function 'foo': testcase.i:2: internal compiler error: Aborted Hope that helps. =] -Chandler PS: delta hates me, and this test case, a lot. reduced it by hand. On Tue, Mar 25, 200...

...(Tr); if (tree_code_type[(int) (((enum tree_code) > (__t)->common.code))] != (tcc_type)) tree_class_check_failed (__t, > (tcc_type), "/home/chandlerc/code/compilers/llvm-gcc/gcc/llvm- > types.cpp", > 81, __FUNCTION__); __t; })->type.size), true) == > getTargetData().getABITypeSizeInBits(Ty)) && "LLVM type size doesn't > match GCC type size!"' failed. > /home/chandlerc/code/compilers/llvm-gcc/gcc/libgcc2.c: In function > '__powixf2': > /home/chandlerc/code/compilers/llvm-gcc/gcc/libgcc2.c:1765: internal > compiler error: Aborted &...

...can be done by a > pointer comparison. Can anyone please suggest me a better way to do it? > > Also, I want to get the size of %struct.S, should I use the following > code? > > const TargetData &TD = getAnalysis<TargetData>(); > unsigned StructSize = > TD.getABITypeSizeInBits(ai->getOperand(0)->getType()); > There are different interpretations of "size" that TargetData supports, but without knowing what you're trying to do, I'd have to guess that this is probably what you want. -- John T. > Thanks a lot. > Lu > _______________...

...n anyone please suggest me a better way > > to do it? > > > > Also, I want to get the size of %struct.S, should I use the > > following code? > > > > const TargetData &TD = getAnalysis<TargetData>(); > > unsigned StructSize = > > TD.getABITypeSizeInBits(ai->getOperand(0)->getType()); > > > There are different interpretations of "size" that TargetData > supports, but without knowing what you're trying to do, I'd have to > guess that this is probably what you want. > > -- John T. > > > Than...

Hi Chandler, > void > foo () { > float x __attribute__ ((mode (XF))); > } nice reduction. I don't see any problem on x86-32, and I don't have access to an x86-64 box right now. Can you please open a PR for this, and also run in the debugger. When you hit the abort, use "up" to go up a stack frame or two or three, and print out the gcc types [use: call

On Wednesday 10 October 2007 12:53, Chris Lattner wrote: > On Mon, 8 Oct 2007, Evan Cheng wrote: > > I am turning 32-bit add into 32-bit LEA on x86-64 but that's > > perfectly legal. Both > > leal (%esi,%edi), %eax > > leal (%rsi,%rdi), %eax > > are legal assembly. It's just the former requires a 67H prefix due to > > the 32-bit address size. >

...sion__ ({ const tree __t = (Tr); if (tree_code_type[(int) (((enum tree_code) (__t)-> common.code))] != (tcc_type)) tree_class_check_failed (__t, (tcc_type), "/home/chandlerc/code/compilers/llvm-gcc/gcc/llvm-types.cpp", 81, __FUNCTION__); __t; })->type.size), true) == getTargetData().getABITypeSizeInBits(Ty)) && "LLVM type size doesn't match GCC type size!"' failed. [New Thread 0x2b709e7b8440 (LWP 15687)] Program received signal SIGABRT, Aborted. [Switching to Thread 0x2b709e7b8440 (LWP 15687)] 0x00002b709e48afa5 in raise () from /lib/libc.so.6 (gdb) up #1 0x00002b709e4...

...me a better way >>> to do it? >>> >>> Also, I want to get the size of %struct.S, should I use the >>> following code? >>> >>> const TargetData &TD = getAnalysis<TargetData>(); >>> unsigned StructSize = >>> TD.getABITypeSizeInBits(ai->getOperand(0)->getType()); >>> >>> >> There are different interpretations of "size" that TargetData >> supports, but without knowing what you're trying to do, I'd have to >> guess that this is probably what you want. >> &...

...({ const tree __t = (Tr); if (tree_code_type[(int) (((enum tree_code) (__t)->common.code))] != (tcc_type)) tree_class_check_failed (__t, (tcc_type), "/llvm-project.official/llvm-gcc-4.0/trunk/gcc/llvm-types.cpp", 82, __FUNCTION__); __t; })->type.size), true) == getTargetData().getABITypeSizeInBits(Ty)) && "LLVM type size doesn't match GCC type size!"' failed. [x86_64-off-dbg]: /llvm-project.official/llvm-gcc-4.0/trunk/gcc/crtstuff.c:194: internal compiler error: Aborted Unfortunately, I don't know enough about gcc internals to really dig into this. If some...

On Mon, 8 Oct 2007, Evan Cheng wrote: > I am turning 32-bit add into 32-bit LEA on x86-64 but that's > perfectly legal. Both > leal (%esi,%edi), %eax > leal (%rsi,%rdi), %eax > are legal assembly. It's just the former requires a 67H prefix due to > the 32-bit address size. > > This does point to a performance problem in the 3 address conversion > code (which I