Displaying 2 results from an estimated 2 matches for "isfunctypeargumentconvert".
2013 Sep 11
0
[LLVMdev] Why a function pointer field in a LLVM IR struct is replaced by {}*?
...FILE
> struct definition. The only difference between these two IR structs is that
> a function pointer type field in the first form is replaced by {}* in the
> second form. Could anyone tell me why this happens and how to disable the
> {}* replacement?
>
>
> See CodeGenTypes::isFuncTypeArgumentConvertible in
clang/lib/CodeGen/CodeGenTypes.cpp; this behavior exists to protect the
type conversion code from infinite recursion. Our behavior could probably
be improved here; patches welcome (but be warned the code is rather
complicated).
Off the top of my head, I can't say why this is triggering...
2013 Sep 11
2
[LLVMdev] Why a function pointer field in a LLVM IR struct is replaced by {}*?
Dear LLVM developers,
My name is Ben Niu and I am a Ph.D. student at Lehigh University. I
compiled the MUSL C library using Clang 3.3, and dumped the generated LLVM
IR files. I found that the MUSL-defined FILE struct (aliasing __FILE_s)
struct __FILE_s {
unsigned flags;
unsigned char *rpos, *rend;
int (*close)(FILE *);
unsigned char *wend, *wpos;
unsigned char *mustbezero_1;