search for: _muldi3

1. I got the tools to build. Yay! 2. I got past all the annoying trouble with not finding header files. Yay! Now I'm having problems with this: llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid I'm investigating this with the debugger and so far I've learned that '<invalid>' seems to be the default constructor for some kind of path object. I d...

...system ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../llvm-gcc4-1.8-source/gcc -I../../llvm-gcc4-1.8-source/gcc/. -I../../llvm-gcc4-1.8-source/gcc/../include -I../../llvm-gcc4-1.8-source/gcc/../libcpp/include -I/home/mykland/llvm/include -I/home/mykland/llvm/include -DL_muldi3 -fvisibility=hidden -DHIDE_EXPORTS -c ../../llvm-gcc4-1.8-source/gcc/libgcc2.c -o libgcc/./_muldi3.o<br> <br> <b>My problem is that when I rerun the command it doesn't fail in the same way. Several things can't be found anymore. The first time the command runs inside the...

...system ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../llvm-gcc4-1.8-source/gcc -I../../llvm-gcc4-1.8-source/gcc/. -I../../llvm-gcc4-1.8-source/gcc/../include -I../../llvm-gcc4-1.8-source/gcc/../libcpp/include -I/home/mykland/llvm/include -I/home/mykland/llvm/include -DL_muldi3 -fvisibility=hidden -DHIDE_EXPORTS -c ../../llvm-gcc4-1.8-source/gcc/libgcc2.c -o libgcc/./_muldi3.o > > My problem is that when I rerun the command it doesn't fail in the > same way. Several things can't be found anymore. The first time the > command runs inside the makefile...

...e/gcc/../include -I../../llvm-gcc4-1.8-source/gcc/../libcpp/include -I/home/mykland/llvm/include -I/home/mykland/llvm/include -iprefix /home/mykland/llvm-gcc/obj/gcc/../lib/gcc/i686-pc-linux-gnu/4.0.1/ -isystem /home/mykland/llvm-gcc/obj/gcc/include -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -DL_muldi3 -DHIDE_EXPORTS -isystem /home/mykland/llvm-gcc/obj/../install//i686-pc-linux-gnu/include -isystem /home/mykland/llvm-gcc/obj/../install//i686-pc-linux-gnu/sys-include -isystem ./include ../../llvm-gcc4-1.8-source/gcc/libgcc2.c -quiet -dumpbase libgcc2.c -mtune=pentiumpro -auxbase-strip libgcc/./_mu...

...c/gcc/../winsup/cygwin/include -DIN_GCC -DDEFAULT_TARGET_MACHINE=\"i686-pc-cygwin\" -W -Wall -Wwrite-st ings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/../include -DL_muldi3 -c ../../src/gcc/libgcc2.c o libgcc/./_muldi3.o gccas: /cygdrive/c/DOCUME~1/Roman/LOCALS~1/Temp/cc1pV5H1.s:29,0: parse error /cygdrive/c/DOCUME~1/Roman/LOCALS~1/Temp/cc1pV5H1.s:29: while reading token: 'target' make[2]: *** [libgcc/./_muldi3.o] Error 1 make[2]: Leaving directory `/tmp/llvm...

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

...e > -I../../llvm-gcc4-1.8-source/gcc/../libcpp/include > -I/home/mykland/llvm/include -I/home/mykland/llvm/include > -iprefix /home/mykland/llvm-gcc/obj/gcc/../lib/gcc/i686-pc-linux-gnu/4.0.1/ -isystem /home/mykland/llvm-gcc/obj/gcc/include -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -DL_muldi3 -DHIDE_EXPORTS -isystem /home/mykland/llvm-gcc/obj/../install//i686-pc-linux-gnu/include -isystem /home/mykland/llvm-gcc/obj/../install//i686-pc-linux-gnu/sys-include -isystem ./include ../../llvm-gcc4-1.8-source/gcc/libgcc2.c -quiet -dumpbase libgcc2.c -mtune=pentiumpro -auxbase-strip libgcc/./_mu...

On Sat, 6 May 2006, Greg Pettyjohn wrote: > Now I'm having problems with this: > > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> > C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid > I've tracked this down in the debugger. It is indeed a bug. The problem is that Path::isValid() will reject a string containing "<" and ">...

..../../llvm-gcc-4.2-2.7.source/gcc -I../../llvm-gcc-4.2-2.7.source/gcc/. -I../../llvm-gcc-4.2-2.7.source/gcc/../include -I../../llvm-gcc-4.2-2.7.source/gcc/../libcpp/include -I../../llvm-gcc-4.2-2.7.source/gcc/../libdecnumber -I../libdecnumber -I/localhome/simmon12/llvm-makefilebuild/include -DL_muldi3 -c ../../llvm-gcc-4.2-2.7.source/gcc/libgcc2.c -o libgcc/./_muldi3.o /localhome/simmon12/aix-cross/obj/./gcc/as: line 2: exec: -u: invalid option Is there anything else I should be doing to build a cross-compiler to generate LLVM bitcode for AIX? My ultimate goal here is just to get a compile...

...eady fixed this in CVS. Please update and give it another shot. Thanks, Reid. On Sat, 2006-05-06 at 16:43 -0400, Greg Pettyjohn wrote: > > On Sat, 6 May 2006, Greg Pettyjohn wrote: > > > Now I'm having problems with this: > > > > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> > > C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid > > > > I've tracked this down in the debugger. It is indeed a bug. The problem is > that Path::isValid() will reject a string containing "...

...DDEFAULT_ TARGET_MACHINE=\"i686-pc-cygwin\" -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NE EDED -I. -I. -I../../../src/llvm-gcc/gcc -I../../../src/llvm-gcc/gcc/. -I../../ ../src/llvm-gcc/gcc/../include -DL_muldi3 -c ../../../src/llvm-gcc/gcc/libgcc2 .c -o libgcc/./_muldi3.o /tmp/cctoZeMj.s: Assembler messages: /tmp/cctoZeMj.s:1: Error: no such instruction: `gnu C version 3.4-llvm 20030924 (experimental)(i686-pc-cygwin)' /tmp/cctoZeMj.s:2: Error: no such instruction: `compiled by GNU C version 3.4.3....

...value. > > -Chris > >> On Sat, 2006-05-06 at 16:43 -0400, Greg Pettyjohn wrote: >>> >>> On Sat, 6 May 2006, Greg Pettyjohn wrote: >>> >>>> Now I'm having problems with this: >>>> >>>> llvm-ar rc ./libgcc.a libgcc/./_muldi3.o >>>> <and-lots-more-.o-files...> >>>> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: >>>> path is not valid >>>> >>> >>> I've tracked this down in the debugger. It is indeed a bug. The >>&...

I was having video problems, so upgraded my Linux box from SUSE 9.3, where LLVM frontend 4 source built fine, to SUSE 10.1, where I got the error message: ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:541: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://llvm.org/bugs> for instructions. This version of SUSE

Hello > ../../llvm-gcc-4.2-2.7.source/gcc/libgcc2.c -o libgcc/./_muldi3.o > /localhome/simmon12/aix-cross/obj/./gcc/as: line 2: exec: -u: invalid option Have you built & installed cross-binutils for your target? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...LT_TARGET_MACHINE=\"ia64-unknown-linux-gnu\" -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I -I../../srcdir/llvm-gcc/gcc -I../../srcdir/llvm-gcc/gcc/ -I../../srcdir/llvm-gcc/gcc/../include -DL_muldi3 -c ../../srcdir/llvm-gcc/gcc/libgcc2.c -o libgcc/./_muldi3.o WARNING: 128 bit integers used, but broken in LLVM! WARNING: 128 bit integers used, but broken in LLVM! gccas: Unknown command line argument '--traditional-format'. Try: 'gccas --help' gmake[2]: *** [libgcc/./_muldi3.o] E...

Fixing one bug uncovers the next one... To reproduce: llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> The result: C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: Can't move './libgcc.a-000003' to './libgcc.a-000002': Cannot create a file when that file already exists. So apparently, we're trying to move one file on top of another....

...cc/. -I../../llvm-gcc4.2/gcc/../include -I../../llvm-gcc4.2/gcc/../libcpp/include -I../../llvm-gcc4.2/gcc/../libdecnumber -I../libdecnumber -I/home/edwin/llvm/llvm-svn/trunk/include -I/home/edwin/llvm/llvm-svn/trunk//include -mkernel -m64 -Dmalloc=kern_os_malloc -Dfree=kern_os_free -DLIBCC_KEXT -DL_muldi3 -fvisibility=hidden -DHIDE_EXPORTS -c ../../llvm-gcc4.2/gcc/libgcc2.c -o libgcc/kext64/_muldi3.o ../../llvm-gcc4.2/gcc/libgcc2.c:1: sorry, unimplemented: 64-bit mode not compiled in make[4]: *** [libgcc/kext64/_muldi3.o] Error 1 make[4]: Leaving directory `/var/local/src/llvm/obj42/gcc' I conf...

...nclude -O2 -DIN_GCC -DDEFAULT_TARGET_MACHINE= \"i386-pc-solaris2.11\" -W -Wall -Wwrite-strings -Wstrict- prototypes -Wmissing-prototypes -isystem ./include -fPIC -g - DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../src/gcc -I../../ src/gcc/. -I../../src/gcc/../include -DL_muldi3 -c ../../src/gcc/ libgcc2.c -o libgcc/./_muldi3.o gccas: This tool is deprecated, please use opt /scratch/llvm-2.0/Release/bin/llvm-as: /var/tmp//ccqeaOYi.s:26,0: / var/tmp//ccqeaOYi.s:26: error: syntax error, unexpected $undefined, expecting TRIPLE or DATALAYOUT while reading token: 'p'...

...to load an archive member without a path set? -Chris > On Sat, 2006-05-06 at 16:43 -0400, Greg Pettyjohn wrote: >> >> On Sat, 6 May 2006, Greg Pettyjohn wrote: >> >>> Now I'm having problems with this: >>> >>> llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> >>> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid >>> >> >> I've tracked this down in the debugger. It is indeed a bug. The problem is >> that Path::isValid() will reject a string...

On Wed, Mar 19, 2008 at 12:11 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Bill, thanks for fixing it. > No prob! :-) > > > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c: In function 'ix86_expand_convert_uns_DI2DF_sse': > > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c:10270: warning: large integer implicitly truncated to unsigned type