Displaying 7 results from an estimated 7 matches for "_2e_str_1".
2004 Jun 19
1
[LLVMdev] MachineOperand: GlobalAddress vs. ExternalSymbol
...ion ; Functions:
declare int %printf(sbyte*, ...)
int %main() {
entry:
%tmp.0.i = call int (sbyte*, ...)*
%printf( sbyte* getelementptr ([11 x sbyte]* %.str_1, long 0, l
ret int 0
}
The assembler produces by X86 backend is:
call printf
........
.globl _2E_str_1
.data
.align 1
.type _2E_str_1, at object
.size _2E_str_1,11
_2E_str_1:
That is, the name of "str1" is mangled, but the name of function is not. I
don't see the reasons for different handling of those two kinds of names.
> > To me this seems a...
2004 Jun 18
0
[LLVMdev] MachineOperand: GlobalAddress vs. ExternalSymbol
On Fri, 18 Jun 2004, Vladimir Prus wrote:
> > actually exist in the LLVM module for the function. In particular, this
> > would include any functions in a code-generator specific runtime library
> > and malloc/free. The X86 code generator compiles floating point modulus
> > into fmod calls, and 64-bit integer div/rem into runtime library calls.
>
> And why isn't
2006 Nov 17
4
[LLVMdev] C++ to C
...hat uses the function:
int main(void) {
struct
l_struct_2E_std_3A__3A_basic_ostream_3C_char_2C_std_3A__3A_char_traits_
3C_char_3E__20__3E_ *ltmp_2_2;
CODE_FOR_MAIN();
/*tail*/ __main();
ltmp_2_2 = /*tail*/
_ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc((
&_ZSt4cout), (&(_2E_str_1[0])));
return 0;
}
Thanks for any tips.
Napi
2004 Jun 18
3
[LLVMdev] MachineOperand: GlobalAddress vs. ExternalSymbol
Chris Lattner wrote:
> > Second, MO_ExternalSymbol is used for storing name of external
> > variable/function, right? Why it's not possible to use MO_GlobalAddress,
> > where returned GlobalValue* has isExternal set to true? The
> > GlobalValue::getName would return the name of the symbol.
>
> Using the GlobalValue is certainly the preferred way if you have it.
2006 Nov 17
0
[LLVMdev] C++ to C
...d) {
> struct
>l_struct_2E_std_3A__3A_basic_ostream_3C_char_2C_std_3A__3A_char_traits_
>3C_char_3E__20__3E_ *ltmp_2_2;
>
> CODE_FOR_MAIN();
> /*tail*/ __main();
> ltmp_2_2 = /*tail*/
>_ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc((
>&_ZSt4cout), (&(_2E_str_1[0])));
> return 0;
>}
>
>Thanks for any tips.
>
>Napi
>
>_______________________________________________
>LLVM Developers mailing list
>LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
2006 Nov 05
0
[LLVMdev] Convert C++ to C. What is 0x0p+0 ?
On Nov 5, 2006, at 2:30 AM, Mohd-Hanafiah Abdullah wrote:
> On Sat, 2006-11-04 at 21:06 -0800, Reid Spencer wrote:
>>> In the resulting file foo.cbe.c there are many occurences of '0x0p
>>> +0'.
>>> What is it used for? Here's a code snippet from the file foo.cbe.c
>>>
>>> if ((ltmp_126_2 > 0x0p+0)) {
>>> goto
2006 Nov 05
4
[LLVMdev] Convert C++ to C. What is 0x0p+0 ?
On Sat, 2006-11-04 at 21:06 -0800, Reid Spencer wrote:
> Hi Napi,
>
> On Sun, 2006-11-05 at 12:40 +0800, Mohd-Hanafiah Abdullah wrote:
> > Hi:
> >
> > I'm interested in using llvm to convert C++ code to C code.
> > I used the following command to do this:
> >
> > % llvm-g++ -c foo.cpp -o - | llc -march=c -o foo.cbe.c
>
> Yup, that'll