Displaying 3 results from an estimated 3 matches for "memory_doubl".
Did you mean:
memory_double
2010 Oct 19
2
[LLVMdev] Structure memory layout
...on type's target dependent problems through long double type on core-utils package.
File isnan.c
28 # define DOUBLE long double
...
66 #define NWORDS \
67 ((sizeof (DOUBLE) + sizeof (unsigned int) - 1) / sizeof (unsigned int))
68 typedef union { DOUBLE value; unsigned int word[NWORDS]; } memory_double;
Because floating point data type isn't allowed to have bitwise operation,
above isnan function converts long double type to unsigned int array whether or not to know "not a number".
I think that both above statements and refered union types problems on your answer are source codes...
2010 Oct 19
0
[LLVMdev] Structure memory layout
On 19 October 2010 07:57, Jin Gu Kang <jaykang10 at imrc.kist.re.kr> wrote:
> Frist, I have been implementing common type for struct type on bitcode
> at compilation time using llvm-gcc and then changing common type to target
> specific types at code generation time using llc (reconstruct StructLayout).
Hi Jin,
Apart from bitfields and unions, the struct type is pretty much target
2010 Oct 19
4
[LLVMdev] Structure memory layout
Hi LLVM members,
I have been working to make target independent memory layout for struct type(Aggregate type) in my team.
I think that struct type has different memory layouts according to each target system in current LLVM.
To implement target dependent concept for struct type,
Frist, I have been implementing common type for struct type on bitcode at compilation time using llvm-gcc and then