search for: gcc's

I can't build llvm-gcc from working directories updated an hour ago. -Dave /tools/llvm-tools/i686-pc-linux-gnu/bin/g++ -c -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -DIN_GCC -W -Wall -Wwrite-strings -pedantic -Wno-long-long -Wno-variadic-macros -fno-common -DHAVE_CONFIG_H -Wno-unused -DTARG...

The machine is a Dell workstation with xeon processors. The OS is RHEL 4 AS x86_64 gcc version is 3.4.6 I checked out the llvm-gcc from svn, configured with ../llvm-gcc/configure --prefix=$HOME/llvm-gcc-install --enable-llvm=$HOME/llvmobj/ --enable-languages=c,c++ --enable-checking --disable-shared --disable-multilib and get the following error message: make GCC_FOR_TARGET="/...

Now I believe that I am getting the same error as I was getting last time I tried to build llvm-gcc. It may possibly be my Cygwin instillation but am not sure. makeinfo --split-size=5000000 -I ../../../src/llvm-gcc/gcc/doc -I ../../../src/ llvm-gcc/gcc/doc/include \ -o ../../../src/llvm-gcc/gcc/doc/cpp.info ../../../src/llvm-gcc/gcc/doc/cpp.texi ' in @synindex.vm-gcc/gcc/doc/cpp.texi:4...

gcc 3.4.x builds LLVM incorrectly on x86_64. gcc 4.0 will get you much farther, but the llvm-test regression tests still have massive problems. Zhongxing Xu wrote: > The machine is a Dell workstation with xeon processors. The OS is RHEL > 4 AS x86_64 > gcc version is 3.4.6 > > I ch...

I am getting an error building svn llvm-gcc on Cygwin :- /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ -B/usr/llv m-gcc/i686-pc-cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem /usr/llvm -gcc/i686-pc-cygwin/include -isystem /usr/llvm-gcc/i686-pc-cygwin/sys-include - O2 -I/home/ang/svn/llvm-gcc/gcc/../winsup...

i am getting this compilation error: gcc -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../llvm-gcc-4.2-2.7.source/gcc...

This is an libpath problem. When xgcc runs it wants to dynamically link the libgcc.so. When you run it from the command line it will find your system libgcc.so (which works) and so you don't see the segfault. When you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get your <cfebuilddir>/gcc directory which w...

At the last step of building llvm for arm target, I am unable to build llvm-gcc. I am trying the follwing options:   $ ../llvm-gcc/configure --target=arm-linux --enable-pic --program-prefix=llvm- --prefix=/llvm/install --disable-multilib --disable-optimized --enable-bindings =none --enable-llvm=$PWD/../llvm-2.8 --enable-languages=c,c++ --disable-bootstr ap   Then I get the fol...

...make clean; make reconfigure; make tools-only) </pre> </blockquote> <b>This all worked great.</b><br> <blockquote cite="mid1162786496.11568.357.camel@bashful.x10sys.com" type="cite"> <pre wrap="">2. Completely rebuild llvm-gcc (wipe out the build dir with rm -rf, configure llvm-gcc and rebuild it) </pre> </blockquote> <b>Okay, got the same error as before.</b><br> <blockquote cite="mid1162786496.11568.357.camel@bashful.x10sys.com" type="cite"> <pre wrap=...

...>::runPasses ()<br> #9  0x0870300f in llvm::PassManagerT<llvm::MTraits>::runOnUnit ()<br> #10 0x086f65eb in llvm::ModulePassManager::runOnModule ()<br> #11 0x086f6659 in llvm::PassManager::run ()<br> #12 0x08256a93 in llvm_asm_file_end ()<br>     at ../../llvm-gcc4-1.8-source/gcc/llvm-backend.cpp:277<br> #13 0x0823bc40 in toplev_main (argc=47, argv=0xbff80804)<br>     at ../../llvm-gcc4-1.8-source/gcc/toplev.c:1171<br> #14 0x08096ad2 in main (argc=-1209859528, argv=0xb7e30240)<br>     at ../../llvm-gcc4-1.8-source/gcc/llvm-main.cpp:37...

Hi! I have just downloaded the R-0.60.1 sources and have problems compiling R on a Sun Ultra 1 running Solaris 2.6 and gcc 2.7.2.1. I have not been able to find to find any compiling hints in the documentation or the FAQ. After ./configure I use make and get the output below. Any hints are welcome. I am not on the list, so please answer me directly too. Best regards Jens --- Jens Lund Ph.D. student in statistics...

On Jan 9, 2007, at 9:48 PM, Jeff Cohen wrote: > gcc 3.4.x builds LLVM incorrectly on x86_64. > > gcc 4.0 will get you much farther, but the llvm-test regression tests > still have massive problems. Please file bug reports on these. Thanks! Evan > > Zhongxing Xu wrote: >> The machine is a Dell workstation with xeon processors....

...id, > > Here's the backtrace you asked for: > > (gdb) bt > #0 0x0862d65c in llvm::LiveVariables::runOnMachineFunction () Hmm, this is a little strange. Your LLVM build is non-debug (there's no line numbers or arguments in any of the llvm related calls). However, your llvm-gcc build seems to have symbols. So, I have some questions: 1. Did you configure llvm-gcc with the --enable-checking option? 2. What did you provide for the --with-llvm= option? llvm-gcc is going to look in that directory for Debug/lib for libraries. So, you should have debug llvm but you don...

I am trying to do some research that involves instrumenting LLVM IR, that I need to test for performance and scalability on a bunch of systems. I've started trying by trying to get sparc-sun-solaris2.10 (niagara) working. It appears that neither llvm nor llvm-gcc will build natively on the system, so I think that I need to build an llvm-gcc cross compiler. The documentation for building gcc (in general) as a cross compiler seems to be somewhat dated... and I'm not a very accomplished gnu hacker. I /think/ that I need to do 5 things. 1) Get the sola...

any ideas what library has these symbols lang_eh_catch_all get_pointer_alignment validate_arglist i get these linker errors when trying to link llvm-gcc: make[1]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree' make[2]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree/build-x86_64-unknown-linux-...

...ered with the name changes. I know nothing of the status of cygwin however, can you confirm that this used to work? If you use r77097, does it work? - Daniel On Sun, Jul 26, 2009 at 4:23 AM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > I am getting an error building svn llvm-gcc on Cygwin :- > > > /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ > -B/usr/llv > m-gcc/i686-pc-cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem > /usr/llvm > -gcc/i686-pc-cygwin/include -isystem > /usr/llvm-gcc/i686-pc-cygwin/sys-include  - &gt...

Hi Aaron, have you got any help on this? Henrik >From: "Aaron Gray" Date: Sat, 14 May 2005 18:26:01 +0100 > >Now I believe that I am getting the same error as I was getting last time I >tried to build llvm-gcc. >It may possibly be my Cygwin instillation but am not sure. > > >makeinfo --split-size=5000000 -I ../../../src/llvm-gcc/gcc/doc -I >../../../src/ >llvm-gcc/gcc/doc/include \ > -o ../../../src/llvm-gcc/gcc/doc/cpp.info >../../../src/llvm-gcc/gcc/doc/cpp.texi >' in...

...vhost_worker_ioctl() error: uninitialized symbol 'vq'. drivers/vhost/vhost.c:774 vhost_worker_ioctl() error: uninitialized symbol 'idx'. {standard input}: Error: local label `"2" (instance number 9 of a fb label)' is not defined Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-randconfig-r002-20230704 | `-- drivers-bluetooth-btmtk.c:error:struct-hci_dev-has-no-member-named-dump |-- loongarch-randconfig-r022-20230704 | `-- drivers-bluetooth-btmtk.c:error:struct-hci_dev-has-no-member-named-dump |-- m68k-randconfig-r016-20230704 | `-- drivers-b...

Hello. My goal is to use LLVM with JIT compiler for ARM on Android device. Currently I have successfully built and executed LLVM bitcode with interpreter on Android. Speed is not so great, that is why I want to use JIT. I tried building bitcode on windows with llvm-gcc that is provided on llvm home page. Resulting bitcode runs great in interpreter, but it doesn't use JIT. From what I understand from LLVM that it is because of target triple or datalayout. On PC in my case target triple is "i386-mingw32", but LLVM JIT for ARM expects something...

Hi Robert, Please make sure that you: 1. Completely rebuild LLVM (make clean; make reconfigure; make tools-only) 2. Completely rebuild llvm-gcc (wipe out the build dir with rm -rf, configure llvm-gcc and rebuild it) If you've done that, then please enter the debugger and get a stack trace for us. You will need to: 1. Capture the xgcc compile command that failed 2. Run that command manually with the -v option to print out the com...