search for: ltmp_0_1

...ed example of some code that results in a CBE short for an > input C/C++ uint32_t ? Hmm the problem was a bit different. I just reproduced it. I used this input file: #include <stdint.h> uint32_t test(uint32_t t) { return(t + 42); } and got the following code: unsigned test(unsigned ltmp_0_1) { return (ltmp_0_1 + 42u); } unsigned is 16 bit on my target platform. Philipp

...Spencer schrieb: > Hmm the problem was a bit different. I just reproduced it. > > I used this input file: > > #include <stdint.h> > > uint32_t test(uint32_t t) > { > return(t + 42); > } > > and got the following code: > > unsigned test(unsigned ltmp_0_1) { > return (ltmp_0_1 + 42u); > } > > unsigned is 16 bit on my target platform. Sure, but what is it on the target that llvm-gcc is configured for? If you're running llvm-gcc on a 32-bit platform without configuring it as a cross-compiler then the above is correct. 32-bit unsign...

...guys. I just wonder if function variables are preserved in the bytecode. For example, are i and j in the following function preserved in .bc? int sum(int i, int j){ int k; k = i + j; return k; } I tested this with "llc -march=c" and found this was converted to int sum(int ltmp_0_1, int ltmp_1_1) { return (ltmp_1_1 + ltmp_0_1); } Therefore, it seems that they are not preserved in the bytecode, right? If it is not, (i.e., they are kept) how can I extract the variables from the bytecode? I got really become to enjoy LLVM's magic. Thank you very much. Seung Jae Lee

Hi Philipp, On Fri, 2006-11-24 at 20:09 +0100, Philipp Klaus Krause wrote: > Reid Spencer schrieb: > > > Note that C and LLVM types are *not* the same things (despite the > > similar names). We are in the process of making this abundantly clear. > > The LLVM IR will soon use names like i8, i16, i32, and i64 (signless > > integer quantities of specific sizes,

...are i and j in the following function preserved in .bc? >> >> int sum(int i, int j){ >> int k; >> k = i + j; >> return k; >> } >> >> I tested this with "llc -march=c" and found this was converted to >> >> int sum(int ltmp_0_1, int ltmp_1_1) { >> return (ltmp_1_1 + ltmp_0_1); >> } >> >> Therefore, it seems that they are not preserved in the bytecode, >> right? >> If it is not, (i.e., they are kept) how can I extract the variables >> from the bytecode? >> I got really...

Reid Spencer schrieb: > Note that C and LLVM types are *not* the same things (despite the > similar names). We are in the process of making this abundantly clear. > The LLVM IR will soon use names like i8, i16, i32, and i64 (signless > integer quantities of specific sizes, regardless of platform). I had explicitly specified the size in the input code using a uint32_t type, the