Displaying 4 results from an estimated 4 matches for "__isoc99_sscanf".
Did you mean:
__isoc99_scanf
2009 Dec 07
1
[LLVMdev] #define LLVM_ASM_PREFIX_CHAR '\1' to make code more readable?
...; fine with me, please don't use a macro though.
I do not like macros either. However, how should I remove magic
numbers from
| } else if (Name == "\1stat64" ||
| Name == "\1lstat64" ||
| Name == "\1statvfs64" ||
| Name == "\1__isoc99_sscanf") {
without using a macro? Something like
| } else if (Name[0] == llvm_asm_prefix && Name.slice(1, 0) == "stat64" ||
| Name[0] == llvm_asm_prefix && Name.slice(1, 0) == "lstat64" ||
| Name[0] == llvm_asm_prefix && Name.slice(1...
2009 Nov 26
0
[LLVMdev] #define LLVM_ASM_PREFIX_CHAR '\1' to make code more readable?
On Nov 18, 2009, at 10:17 AM, Timo Juhani Lindfors wrote:
> Hi,
>
> llvm, clang and llvm-gcc contain numerous references to 1, '\1',
> '\01', '\001', "\01" and "\01foo". This makes it difficult for one to
> find all occurences of this prefix character and lacks a central place
> where the prefix could be documented. (See for example
2011 Jun 02
5
Problems with wine & Crossover Pro after upgrading to Kubunt
...)
1 0xf74d08b7 in libc.so.6 (+0x6a8b6) (0x020fdddc)
2 0xf74b5053 __isoc99_vsscanf+0x72() in libc.so.6 (0x020fdea0)
3 0xf74b4fcf __isoc99_sscanf+0x1e() in libc.so.6 (0x020fdeb4)
4 0x7e054137 in wined3d (+0x54136) (0x020fe074)
5 0x7e05864e in wined3d (+0x5864d) (0x020fe504)
6 0x7e05c311 in wined3d (+0x5c310) (0x020fe524)
7 0x7e0e344a wined3d_create+0x59() in wined3d (0x020fe564)
8 0x7d825e2f Direct3DCreate9+0x5e() in d3d9 (0x020fe5...
2009 Nov 18
2
[LLVMdev] #define LLVM_ASM_PREFIX_CHAR '\1' to make code more readable?
Hi,
llvm, clang and llvm-gcc contain numerous references to 1, '\1',
'\01', '\001', "\01" and "\01foo". This makes it difficult for one to
find all occurences of this prefix character and lacks a central place
where the prefix could be documented. (See for example
http://llvm.org/bugs/show_bug.cgi?id=5480 )
How about adding a #define for this prefix?