search for: torrec

hi, I want to know what is exact meaning in the following code. target endian-- %struct..TorRec-- %struct.TorRec-- implementation-- ;<sbyte>[#uses=1/0]-- how to explain them in details? Does anyone give me a guide? thanks yueqiang -------------------------------------------------------------- target endian = little target pointersize = 32 %struct..TorRec = type { int, void ()...

...<stdlib.h> char a[20]="global string test\n"; int main( int argc , char *argv[]){ char b[20]= "Internal string test"; printf("Global %s \n",a); printf("Internal %s\n",b); } IR code : target endian = little target pointersize = 32 %struct..TorRec = type { int, void ()* } %struct.TorRec = type { int, void ()* } %a = internal global [20 x sbyte] c"global string test\0A\00" ; <[20 x sbyte]*> [#uses=1] %.ctor_1 = internal global [20 x sbyte] c"Internal string test" ; <[20 x sbyte]*> [#uses=1] %.str_1 = interna...

On Tue, 30 Nov 2004, Tanu Sharma wrote: > I have trouble using the llvm tools.Some of the errors are : > > $ llvm-dis prog.bc > $ llvm-dis: Invalid Top Level Block Length! Type:1, Size:456 (Vers=0, Pos=12) Can you explain how you generated this bytecode file? It looks corrupted or something. Also, can you send the actual bytecode file itself? Thanks! -Chris >

...he bytecode file and it works fine with llvm-bcanalyzer and llvm-dis. The output from those tools are attached. So, I think the real question is: "what llvm-dis where you running?". Reid. -------------- next part -------------- target endian = little target pointersize = 32 %struct..TorRec = type { int, void ()* } %struct.TorRec = type { int, void ()* } %.str_1 = internal constant [24 x sbyte] c"This is main function \0A\00" ; <[24 x sbyte]*> [#uses=1] %.str_2 = internal constant [21 x sbyte] c"Calling sub function\00" ; <[21 x sbyte]*> [#uses=1] %....

hi, how to explain the following two statement in detail? (1) %struct.TorRec = type { int, void ()* } (2) "struct._GLOBAL__N_::vtable_prefix" = type { int, "struct.__cxxabiv1::__class_type_info"*, sbyte* } yueqiang

The -c option tells llvm-gcc to build a bytecode file without linking in the LLVM runtime library. This is similar to the -c option for regular gcc, which you use to build multiple separate .o files that you're going to link into a single executable. If you want to build from a single source file, it's easiest just to compile without the -c option. If you're building from

Hello, When I compile a "hello.c" program with a printf in "main" and use llvm-gcc with a "-c" option: llvm-gcc -c t1.c -o t1.bc and then try to compile t1.bc to native using llc & gcc I get a call to "__main" which is undefined. If I don't use the "-c" option: llvm-gcc t1.c -o t1 I don't get a reference to

> Ok, I am developing an intrinsic instruction and I have the codegen > working (and tested). However, some of the more complex cases of the > intrinsic are reducable to LLVM + simpler cases of the intrinsic. How > would I go about conditionally reducing the intrinsic? I could deal > with the issue in the codegen, but that gets ugly quickly. > > Andrew I suppose you could

...ot;-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not call __main: ----------------------- ; ModuleID = '<stdin>' target endian = little target pointersize = 32 target triple = "i686-pc-linux-gnu" deplibs = [ "c", "crtend" ] %struct..TorRec = type { int, void ()* } %struct.TorRec = type { int, void ()* } %.str_1 = internal constant [4 x sbyte] c"yo\0A\00" ; <[4 x sbyte]*> [#uses=1] implementation ; Functions: declare int %printf(sbyte*, ...) int %main(int %argc, sbyte** %argv) { entry: %tmp.0 = tai...

Ok, I am developing an intrinsic instruction and I have the codegen working (and tested). However, some of the more complex cases of the intrinsic are reducable to LLVM + simpler cases of the intrinsic. How would I go about conditionally reducing the intrinsic? I could deal with the issue in the codegen, but that gets ugly quickly. Andrew -------------- next part -------------- A non-text

...O^@^G^@^G^C^Y^B^O^@^G^@^G������"^@^@^@^@������"^@^@^@^@������^B^Q^@^@^@����^G^F^@^@]^Q^P^@^K<8c>^P^Hb^Q^A^A ^L ^@p^R^B^A^A������p^R^B^A^B������p^R��r^U^A^A^E^G^@^@��^H^@^@^@^A^A^B^Gtmp.1.i^C^G^B^Etmp.0^D^Gtmp.0.i^C^Etmp.2^C^L^L__main.entry^A endif.0.i^@^Eentry��$^M^@^@^B^Y^Nstruct..TorRec^Y^Mstruct.TorRecB^O^A^F.str_2^B^F.str_3^A^R^A^Fprintf^A^U^A^Dexit^A^W^A^Dmain^A^M^A^F.str_1^A^Q^A^OInitialized.0__������ ------------------------------------------------------------------------------- I generated it like this: $llvmgcc prog.c -o prog Thanks Tanu Chris Lattner <sabre at n...

...ng pass which reduces the > complex cases to the simple cases. This would then allow you to use > the redundancy-elimination passes like LICM to clean up the resulting > code. > > -Brian -------------- next part -------------- target endian = little target pointersize = 32 %struct..TorRec = type { int, void ()* } %struct.TorRec = type { int, void ()* } %struct.timeval = type { int, int } %typedef.__sigset_t = type { [32 x uint] } %typedef.fd_set = type { [32 x int] } %typedef.pthread_mutexattr_t = type { int } %union.nfsctl_res3. = type opaque %.str_1 = internal constant [13 x...

..."Internal string test"; > > > > printf("Global %s \n",a); > > printf("Internal %s\n",b); > > > > } > > > > > > IR code : > > > > target endian = little > > target pointersize = 32 > > %struct..TorRec = type { int, void ()* } > > %struct.TorRec = type { int, void ()* } > > %a = internal global [20 x sbyte] c"global string test\0A\00" ; <[20 x sbyte]*> [#uses=1] > > %.ctor_1 = internal global [20 x sbyte] c"Internal string test" ; <[20 x sbyte]*&g...