Displaying 2 results from an estimated 2 matches for "test1_t".
2009 Sep 22
3
[LLVMdev] StructLayout
...etTypePaddedSize(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 in LLVM is:
%test1 = type { i10, i5, i1, i45 }
to have size 12 on x86-64 whien it should have size 8.
I don't know how to work around this since the original bitfield type has been
lost by the time we translate to LLVM.
Does this need to be handled in the frontend, to munge the st...
2009 Sep 23
0
[LLVMdev] StructLayout
...> 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 in LLVM is:
>
> %test1 = type { i10, i5, i1, i45 }
>
> to have size 12 on x86-64 whien it should have size 8.
>
> I don't know how to work around this since the original bitfield type has
> been
> lost by the time we translate to LLVM.
>
> Does thi...