Displaying 3 results from an estimated 3 matches for "dhost_words_big_endian".
2004 May 05
0
[LLVMdev] Testing LLVM on OS X
...We will use: 176.gcc
Compiling Binaries
Building 176.gcc ref base ppc32_llvm default
specmake clean 2> make.err | tee make.out
rm -rf cc1 cc1.exe *.o core *.err *.out
specmake build 2> make.err | tee make.out
/Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o
c-parse.o -DHOST_WORDS_BIG_ENDIAN -O3 c-parse.c
/Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o
c-lang.o -DHOST_WORDS_BIG_ENDIAN -O3 c-lang.c
/Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o
c-lex.o -DHOST_WORDS_BIG_ENDIAN -O3 c-lex.c
/Users/patrick/Desktop/LLVM/...
2004 May 04
6
[LLVMdev] Testing LLVM on OS X
On Tue, 4 May 2004, Chris Lattner wrote:
> I suspect that a large reason that LLVM does worst than a native C
> compiler with the CBE+GCC is that LLVM generates very low-level C code,
> and I'm not convinced that GCC is doing a very good job (ie, without
> syntactic loops).
Yup, this is EXACTLY what is going on.
I took this very simple C function:
int Array[1000];
void test(int
2004 May 05
2
[LLVMdev] Testing LLVM on OS X
...ng Binaries
> Building 176.gcc ref base ppc32_llvm default
> specmake clean 2> make.err | tee make.out
> rm -rf cc1 cc1.exe *.o core *.err *.out
> specmake build 2> make.err | tee make.out
> /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o
> c-parse.o -DHOST_WORDS_BIG_ENDIAN -O3 c-parse.c
> /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o
> c-lang.o -DHOST_WORDS_BIG_ENDIAN -O3 c-lang.c
> /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o
> c-lex.o -DHOST_WORDS_BIG_ENDIAN -O3 c-lex.c
> /User...