Displaying 2 results from an estimated 2 matches for "__file_s".
Did you mean:
__file__
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;
unsigned char *wbase;
size_t (*read)(FILE *, unsigned char *, size_t);
size_t (*write)(FILE *, const unsigned char *, size_t...
2013 Sep 11
0
[LLVMdev] Why a function pointer field in a LLVM IR struct is replaced by {}*?
...Ben Niu <niuben003 at gmail.com> wrote:
> 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;
> unsigned char *wbase;
> size_t (*read)(FILE *, unsigned char *, size_t);
> size...