Displaying 3 results from an estimated 3 matches for "gcc464".
Did you mean:
gcc44
2014 Oct 28
2
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
...e
> source tree" so as to prevent polluting of the source tree, I saw a
> recommendation to build *within* the source tree, so I rolled back and
> built LLVM3.3 *in the source tree* (GASP!) for native (x86_64). In sum, to
> build DragonEgg I used something like
> GCC=/path/to/gcc464/bin/gcc
> LLVM_CONFIG=/path/to/llvm-3.3.src-x86_64/prefix/bin/llvm-config make
>
> * Then to use this shiny new .so, I started by going only up to the point
> of emitting LLVM IR so as not to confuse the situation with further
> architecture-specific compilation/assembly:
> /pa...
2014 Oct 28
3
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
...uting of the source tree, I saw a
> >> recommendation to build *within* the source tree, so I rolled back and
> built
> >> LLVM3.3 *in the source tree* (GASP!) for native (x86_64). In sum, to
> build
> >> DragonEgg I used something like
> >> GCC=/path/to/gcc464/bin/gcc
> >> LLVM_CONFIG=/path/to/llvm-3.3.src-x86_64/prefix/bin/llvm-config make
> >>
> >> * Then to use this shiny new .so, I started by going only up to the
> point
> >> of emitting LLVM IR so as not to confuse the situation with further
> >> archi...
2014 Oct 28
2
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
I am using a gcc (v 4.8.2) cross compiler for the tilera architecture.
There is an LLVM (v 3.3) cross compiler available for tilera (
http://tilera.github.io/llvm),
but the frontend only has partial support for certain tilera intrinsics and
no OpenMP support.
Hence, I have decided to use DragonEgg (v 3.3) to resolve this. I was able
to build
DragonEgg, but when I pass the command line argument