search for: l8_indvar

...ce code, good GCC. :) Okay, I changed the C backend to emit syntactic loops around the real loops, and it seems to make a big difference. LLVM now generates this code (note that the actual loop is not actually responsible for control flow, it's unreachable): void test(int l7_X) { unsigned l8_indvar; unsigned l8_indvar__PHI_TEMPORARY; int *l14_tmp_2E_4; int l7_tmp_2E_7; unsigned l8_indvar_2E_next; l8_indvar__PHI_TEMPORARY = 0u; /* for PHI node */ goto l13_no_exit; do { /* Syntactic loop 'no_exit' to make GCC happy */ l13_no_exit: l8_indvar = l8_indvar__PHI_TEMPO...

On Tue, 4 May 2004, Patrick Flanagan wrote: > I was able to run through all the C/C++ benchmarks in SPEC using LLVM. > I'm on OS X 10.3.3. I did a quick comparison between LLVM (latest from > CVS as of 4/27) and gcc 3.3 (Apple's build 20030304). For simplicity's > sake, the only flag I used was -O3 for each compiler and I was using > the C backend to generate native

I was able to run through all the C/C++ benchmarks in SPEC using LLVM. I'm on OS X 10.3.3. I did a quick comparison between LLVM (latest from CVS as of 4/27) and gcc 3.3 (Apple's build 20030304). For simplicity's sake, the only flag I used was -O3 for each compiler and I was using the C backend to generate native code for PPC. Most of the LLVM results were close to gcc

...stwx r6,r2,r9 ; store addi r2,r2,4 ; Increment pointer bdnz L9 ; Decrement count register, branch while not zero blr This is nice code, good GCC. :) Okay, LLVM currently generates this code from the CBE: void test(int l7_X) { unsigned l8_indvar; unsigned l8_indvar__PHI_TEMPORARY; int *l14_tmp_2E_5; int l7_tmp_2E_9; unsigned l8_indvar_2E_next; l8_indvar__PHI_TEMPORARY = 0u; /* for PHI node */ l13_no_exit: l8_indvar = l8_indvar__PHI_TEMPORARY; l14_tmp_2E_5 = &Array[l8_indvar]; l7_tmp_2E_9 = *l14_tmp_2E_5; *l14_tmp_...