Displaying 2 results from an estimated 2 matches for "mustbezero_2".
Did you mean:
mustbezero_1
2013 Sep 11
2
[LLVMdev] Why a function pointer field in a LLVM IR struct is replaced by {}*?
...eek)(FILE *, off_t, int);
unsigned char *buf;
size_t buf_size;
FILE *prev, *next;
int fd;
int pipe_pid;
long lockcount;
short dummy3;
signed char mode;
signed char lbf;
int lock;
int waiters;
void *cookie;
off_t off;
char *getln_buf;
void *mustbezero_2;
unsigned char *shend;
off_t shlim, shcnt;};
was represented by
%struct.__FILE_s = type { i32, i8*, i8*,
i32 (%struct.__FILE_s*)*, i8*, i8*, i8*, i8*,
i64 (%struct.__FILE_s*, i8*, i64)*,
i64 (%struct.__FILE_s*, i8*, i64)*,
i64 (%struct.__FILE_s*, i64, i32)*,
i8*, i64, %struct.__FILE_s*, %...
2013 Sep 11
0
[LLVMdev] Why a function pointer field in a LLVM IR struct is replaced by {}*?
...size;
> FILE *prev, *next;
> int fd;
> int pipe_pid;
> long lockcount;
> short dummy3;
> signed char mode;
> signed char lbf;
> int lock;
> int waiters;
> void *cookie;
> off_t off;
> char *getln_buf;
> void *mustbezero_2;
> unsigned char *shend;
> off_t shlim, shcnt;};
>
> was represented by
>
> %struct.__FILE_s = type { i32, i8*, i8*,
> i32 (%struct.__FILE_s*)*, i8*, i8*, i8*, i8*,
> i64 (%struct.__FILE_s*, i8*, i64)*,
> i64 (%struct.__FILE_s*, i8*, i64)*,
> i64 (%struct.__FIL...