Displaying 4 results from an estimated 4 matches for "__isoc99_fscanf".
2012 Dec 25
0
[LLVMdev] [DragonEgg] Strange call to @"\01__isoc99_fscanf"
> While testing a File I/O sample program, I've encountered a link failure due
> to missing implementation of "\01__isoc99_fscanf" function. I think this
> function should be named "__isoc99_fscanf" instead. Please see the program
> code and LLVM IR generated by DragonEgg and clang below. It shows that clang
> generates "__isoc99_fscanf", while DragonEgg gives "\01__isoc99_fscanf"....
2010 May 29
3
[LLVMdev] "\01__isoc99_fscanf"
I have a bitcode file Y that has a symbol __isoc99_fscanf in it. When
I disassemble the bitcode, the symbol is written as
"\01__isoc99_fscanf". I am wondering where this symbol is coming from?
I grep'ed throughout /usr on my machine for both names, and I only
found __isoc99_fscanf, without the special character in front.
Regardless...
2012 Dec 25
2
[LLVMdev] [DragonEgg] Strange call to @"\01__isoc99_fscanf"
Dear all,
First of all, Merry Christmas! :)
While testing a File I/O sample program, I've encountered a link failure
due to missing implementation of "\01__isoc99_fscanf" function. I think
this function should be named "__isoc99_fscanf" instead. Please see the
program code and LLVM IR generated by DragonEgg and clang below. It shows
that clang generates "__isoc99_fscanf", while DragonEgg gives
"\01__isoc99_fscanf". We generally us...
2010 May 29
0
[LLVMdev] "\01__isoc99_fscanf"
On 29 May 2010 02:43, Ryan M. Lefever <lefever at illinois.edu> wrote:
> I have a bitcode file Y that has a symbol __isoc99_fscanf in it. When
> I disassemble the bitcode, the symbol is written as
> "\01__isoc99_fscanf". I am wondering where this symbol is coming from?
> I grep'ed throughout /usr on my machine for both names, and I only
> found __isoc99_fscanf, without the special character in fron...