similar to: [LLVMdev] configuring cross compiler for Mac to Linux on ARM

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] configuring cross compiler for Mac to Linux on ARM"

2009 Jul 03
0
[LLVMdev] llvm-gcc cross compiler for ARM Linux failing
On Jul 2, 2009, at 6:24 PM, Neel Nagar wrote: > I suspect that my llvm-gcc cross compiler is using the wrong > assembler because it does not recognize "-mcpu=cortex-a8". This is a known problem. We've only added support for ARMv7 (including cortex-a8) in llvm in the last week or so, and the associated changes for llvm-gcc are still pending. Unless you need specific
2009 Jul 03
4
[LLVMdev] llvm-gcc cross compiler for ARM Linux failing
I suspect that my llvm-gcc cross compiler is using the wrong assembler because it does not recognize "-mcpu=cortex-a8". I was trying to build a cross compiler for a Mac host. Now I am trying to build on x86_64 Linux. I am targeting a Beagle board with an ARM Cortex-A8 and Angstrom Linux. TRIED: to use the script in llvm/utils/crosstool/ARM/build-install-linux.sh I used the recommended
2009 Jul 03
1
[LLVMdev] llvm-gcc cross compiler for ARM Linux failing
Hello Anton, Thanks for replying. The message "as: unrecognized option `-mcpu=cortex-a8'" is the same message I get when I just enter: as -mcpu=cortex-a8 So I think I llvm-gcc is using the Linux i386 assembler to assemble ARM code. Not good. What assembler is it supposed to use? The one in CodeSourcery? > But how's assembler actually called? Just try to compile
2008 Nov 01
0
[LLVMdev] llvm-gcc-4.2 CC1_SPECS
On Fri, Oct 31, 2008 at 10:38:50AM -0700, Mike Stump wrote: > On Oct 31, 2008, at 9:40 AM, Jack Howarth wrote: >> However in current llvm svn, when I compile code with llvm-gfortran, I >> get these warning >> flags passed by default so that I get bogus warnings of... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/ >>
2013 Jul 17
0
opusfile, compiler warnings
Just a report about compiler warnings generated when building opusfile from current git. Regards. # x86-Linux builds / gcc48 and clang-3.3 (no warnings) # x86-Linux builds / gcc34 src/opusfile.c: In function `op_calc_bitrate': src/opusfile.c:1777: warning: integer constant is too large for "long" type src/opusfile.c: In function `op_open2': src/opusfile.c:1131: warning:
2008 Dec 17
2
[LLVMdev] ICE while building llvm-gcc
Thanks for the quick answer! Syncing to r61112 got rid of the ICE, but I still get the following error: make "DESTDIR=" "RPATH_ENVVAR=DYLD_LIBRARY_PATH" "TARGET_SUBDIR=i686-apple-darwin9" "bindir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/bin" "datadir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/share"
2009 Apr 08
4
[LLVMdev] What is the state of LLVM's ARM backend
Hello Evan and Robert I have been investigating the unexpected test failures from the ARM nightly builders in order to get a better picture why the ARM backend don't pass the whole testsuite: I have run the failing tests manually on my arm board and can now categorize most of the thirteen unexpected CodeGen failures in four categories: 1. llvm don't lower MVT::i64 properly on arm
2009 Mar 25
1
Angstrom Symbol on Y-axis ?
Hi, I have started very recently with R in order to get excellent Box and Whisker plots. I could plot my data nicely. However, I can't figure out from R-mailing list archive or google search either, how to place an Angstrom sign/symbol on the y-axis (any axis in principle), after a usual y-axis label ? I am doing something like this:
2009 Jul 03
0
[LLVMdev] llvm-gcc cross compiler for ARM Linux failing
Hi, Neel > I suspect it is using the wrong assembler. But when I do llvm-gcc -v I > can see it has: > >  --with-gnu-as=/home/neel/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-as But how's assembler actually called? Just try to compile something with extra -v option added -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg
2009 Apr 08
2
[LLVMdev] What is the state of LLVM's ARM backend
Duncan Sands skrev: > Hi Xerxes, > > >> 4. softfloat related errors >> http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/softenfloat_Do_not_know_how_to_soften_the_result_of_this_operator/ >> example: >> >> root at overo:/home/xerxes/llvm-test/fail/CodeGen/softenfloat# llvm-as < 2007-11-19-VectorSplitting.ll | llc >>
2008 Dec 16
2
[LLVMdev] ICE while building llvm-gcc
I'm on OSX 10.5, trying to build a svn checkout of llvm-gcc. I've also checked out llvm. Both are synced to r61075. I'm using Apple's gcc 4.0.1: $ gcc -v Using built-in specs. Target: i686-apple-darwin9 Configured with: /var/tmp/gcc/gcc-5488~2/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++
2009 Mar 05
1
[LLVMdev] Fwd: PPC Nightly Build Result
FYI: It also showed up for ARM yesterday, but only for a non-debug build. On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote: > Hi Bill, > > this might be a latent bug related to PPC. I have no such > machine to access atm., but I shall be able to reproduce the > problem when back at home. (In about 4 hours). > > I keep you informed. > > Cheers, > > Gabor >
2008 Feb 16
2
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
> > Using built-in specs. > Target: i686-apple-darwin9 > Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ > src/configure --disable-checking --enable-werror --prefix=/Developer/ > usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man -- > enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program- >
2009 Jan 24
1
[LLVMdev] -O4 limitations in llvm/llvm-gcc-4.2 2.5?
What exactly are the current limitations for using -O4 to create shared libraries with llvm/llvm-gcc-4.2 2.5? I tried a build of xplor-nih at -O4 with llvm-gcc, llvm-g++ and llvm-gfortran. The build fails to link shared libraries with errors such as... Building xplor-nih for platform: Darwin_9_x86 [ -d /Users/howarth/xplor-nih-2.21/bin.Darwin_9_x86/ ] || mkdir
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 12:55 PM, Dale Johannesen wrote: >> >> Using built-in specs. >> Target: i686-apple-darwin9 >> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ >> src/configure --disable-checking --enable-werror --prefix=/Developer/ >> usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man -- >>
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
llvm itself is built with gcc-4.0, but the run line is: // RUN: %llvmgxx -S -O0 -emit-llvm %s -o - | grep retval | grep S242 | grep {i32 1} | count 2 According the log: FAIL: /Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+ +Frontend/2008-02-13-sret.cpp Failed with exit(1) at line 1 while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /
2009 Apr 08
0
[LLVMdev] What is the state of LLVM's ARM backend
Hi Xerxes, > 4. softfloat related errors > http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/softenfloat_Do_not_know_how_to_soften_the_result_of_this_operator/ > example: > > root at overo:/home/xerxes/llvm-test/fail/CodeGen/softenfloat# llvm-as < 2007-11-19-VectorSplitting.ll | llc > SoftenFloatResult #0: 0x614e00: f32 = undef > llc:
2008 Feb 18
1
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 2:35 PM, Tanya Lattner wrote: > On Feb 16, 2008, at 12:55 PM, Dale Johannesen wrote: >>> Using built-in specs. >>> Target: i686-apple-darwin9 >>> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ >>> src/configure --disable-checking --enable-werror --prefix=/ >>> Developer/ >>> usr/llvm-gcc-4.2
2009 Mar 05
0
[LLVMdev] Fwd: PPC Nightly Build Result
Hi Bill, this might be a latent bug related to PPC. I have no such machine to access atm., but I shall be able to reproduce the problem when back at home. (In about 4 hours). I keep you informed. Cheers, Gabor On Mar 4, 7:57 pm, Bill Wendling <wendl... at apple.com> wrote: > Something last night broke the build on Darwin PPC. Possible Gabor's   > check-in? > > -bw
2010 Feb 15
3
[LLVMdev] Botched Build
On Feb 15, 2010, at 1:17 PM, David Greene wrote: > On Monday 15 February 2010 15:08:22 Chris Lattner wrote: >> On Feb 15, 2010, at 1:04 PM, David Greene wrote: >>>> FWIW, this is because you broke the encoding of an instruction in your >>>> patch. This is incorrect: >>>> >>>> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins