search for: yendi

Still nothing here: [yendi:~] echristo% llvm-gcc -march=nocona foo.c -S -arch x86_64 [yendi:~] echristo% So, perhaps you could send more information? Or bug the mac ports people. -eric On Aug 22, 2011, at 2:44 PM, Nichols A. Romero wrote: > This comes up when trying to compile Valgrind, here is the full compile line:...

...naromero:~/pmr] naromero% llvm-gcc -march=nocona pow.c -S -arch x86_64 cc1: error: unrecognized command line option "-arch" Not that this macport is using LLVM 2.9. On Mon, Aug 22, 2011 at 4:46 PM, Eric Christopher <echristo at apple.com> wrote: > Still nothing here: > > [yendi:~] echristo% llvm-gcc -march=nocona foo.c -S -arch x86_64 > [yendi:~] echristo% > > So, perhaps you could send more information? Or bug the mac ports people. > > -eric > > On Aug 22, 2011, at 2:44 PM, Nichols A. Romero wrote: > >> This comes up when trying to compile V...

This comes up when trying to compile Valgrind, here is the full compile line: /opt/local/bin/llvm-gcc-4.2 -Wbad-function-cast -Wcast-qual -Wcast-align -fstrict-aliasing \ -arch x86_64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -mmacosx-version-min=10.5 -fno-stack-protector \ -O -S

...rch=nocona pow.c -S -arch x86_64 > cc1: error: unrecognized command line option "-arch" > > Not that this macport is using LLVM 2.9. > > On Mon, Aug 22, 2011 at 4:46 PM, Eric Christopher <echristo at apple.com> wrote: >> Still nothing here: >> >> [yendi:~] echristo% llvm-gcc -march=nocona foo.c -S -arch x86_64 >> [yendi:~] echristo% >> >> So, perhaps you could send more information? Or bug the mac ports people. >> >> -eric >> >> On Aug 22, 2011, at 2:44 PM, Nichols A. Romero wrote: >> >>&gt...

...> >>> --Liu >>> <Mips-td-comment-type-error.patch> >> >> Looks fine. Do you need someone to apply this for you? >> >> -eric >> > > Hi Eric > > I'm so glad someone apply this to me. Will you? > Thanks. Applied here: [yendi:Data/sources/llvm] echristo% svn ci lib/Target/Mips/ Sending lib/Target/Mips/MipsInstrFPU.td Sending lib/Target/Mips/MipsInstrFormats.td Sending lib/Target/Mips/MipsInstrInfo.td Transmitting file data ... Committed revision 131086. -eric

On Sat, May 7, 2011 at 12:33 PM, Eric Christopher <echristo at apple.com> wrote: > > On May 5, 2011, at 11:26 PM, Liu wrote: > >>  some some type errors in the commentary of *.td file. >> such as: >> lib/Target/Mips/MipsInstrFormats.td >> MipsRegisterInfo.td - Mips Register defs >> it should be >> MipsInstrFormats.td - Mips Instruction Formats

...>> cc1: error: unrecognized command line option "-arch" >> >> Not that this macport is using LLVM 2.9. >> >> On Mon, Aug 22, 2011 at 4:46 PM, Eric Christopher <echristo at apple.com> wrote: >>> Still nothing here: >>> >>> [yendi:~] echristo% llvm-gcc -march=nocona foo.c -S -arch x86_64 >>> [yendi:~] echristo% >>> >>> So, perhaps you could send more information? Or bug the mac ports people. >>> >>> -eric >>> >>> On Aug 22, 2011, at 2:44 PM, Nichols A. Romero...

Hi, I apologize if I am not asking on the right mailing list. I am using the llvm-gcc4.2 from MacPorts. https://trac.macports.org/browser/trunk/dports/lang/llvm-gcc42/Portfile llvm-gcc does not seem to accept the -march flag. This is the error, I got: cc1: error: unrecognized command line option "-march" The port developer asked me to find out if this is a known issue. -- Nichols

...ecognized command line option "-arch" >>> >>> Not that this macport is using LLVM 2.9. >>> >>> On Mon, Aug 22, 2011 at 4:46 PM, Eric Christopher <echristo at apple.com> wrote: >>>> Still nothing here: >>>> >>>> [yendi:~] echristo% llvm-gcc -march=nocona foo.c -S -arch x86_64 >>>> [yendi:~] echristo% >>>> >>>> So, perhaps you could send more information? Or bug the mac ports people. >>>> >>>> -eric >>>> >>>> On Aug 22, 2011, at 2:...

Hello, I haven't yet received any input what this patch breaks (some LLVM-external project?) and the branch creation date is tomorrow. Can someone please tell what we can do to make this patch merged in for 2.8? Thanks! On 07/06/2010 01:26 PM, Pekka Jääskeläinen wrote: > Hello, > > This patch was reverted and the revert was forgotten to be undone > after the performance

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

...you're running, very simply? It's only about 10 lines. > > Comments: > > a) If you've got a failing configure then not re-running configure for > subdirectories isn't likely to change anything is it? > > b) In a grep of my llvm build directory I have: > > [yendi:Data/builds/build-llvm] echristo% grep EMITIR * > Makefile.config:LLVMCC_EMITIR_FLAG = -emit-llvm > config.log:LLVMCC_EMITIR_FLAG='-emit-llvm' > config.status:s, at LLVMCC_EMITIR_FLAG@,|#_!!_#|-emit-llvm,g > > If you've done your configure correctly you'll see somethi...