Displaying 7 results from an estimated 7 matches for "loptflags".
Did you mean:
optflags
2011 Jan 16
2
[LLVMdev] About test suits Cont1
*[qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {}
\;*
./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS)
$(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS)
$(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
./projects/test-suite/Makefile.tests:55: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS)
$(LOPTFLAGS) $(X_TARGET_FLA...
2011 Jan 17
0
[LLVMdev] About test suits Cont1
On Jan 15, 2011, at 8:06 PM, Qingan Li wrote:
> [qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {} \;
> ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
> ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
> ./projects/test-suite/Makefile.tests:55: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_...
2011 Jan 18
3
[LLVMdev] About test suits Cont1
...11/1/18 Eric Christopher <echristo at apple.com>
>
> On Jan 15, 2011, at 8:06 PM, Qingan Li wrote:
>
> [qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {}
> \;
> ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS)
> $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
> ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS)
> $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
> ./projects/test-suite/Makefile.tests:55: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS)
> $(LOPTF...
2011 Jan 14
0
[LLVMdev] About test suits Cont
On Jan 13, 2011, at 6:22 PM, Qingan Li wrote:
> make[4]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource/UnitTests/Vector/SSE'
> /home/qali/Src/llvm-2.8/autoconf/mkinstalldirs Output > /dev/null
> /home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc -I/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource/UnitTests/Vector/SSE
2011 Jan 14
2
[LLVMdev] About test suits Cont
[qali at qali test-suite]$ make VERBOSE=1
if [ ! -f SingleSource/Makefile ]; \
then \
/home/qali/Src/llvm-2.8/autoconf/mkinstalldirs SingleSource; \
cp /home/qali/Src/llvm-2.8/projects/test-suite/SingleSource/Makefile
SingleSource/Makefile; \
fi; \
make -C SingleSource all
make[1]: Entering directory
`/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource'
if [ ! -f UnitTests/Makefile
2011 Jan 19
0
[LLVMdev] Fwd: About test suits Cont1
...011/1/18 Eric Christopher <echristo at apple.com>
>
> On Jan 15, 2011, at 8:06 PM, Qingan Li wrote:
>
> [qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {}
> \;
> ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS)
> $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
> ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS)
> $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
> ./projects/test-suite/Makefile.tests:55: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS)
> $(LOPTF...
2011 Nov 09
1
[LLVMdev] Difference in behavior between local machine and buildbot
...bin/llvm-g++ … -S spirit.cpp -o Output/spirit.ll -emit-llvm
Trouble is, llvm-g++ emits an .ll file which isn't valid so llvm-as fails on my machine.
I've looked at the makefiles for the test suite and it seems that this command is the one being run here
-$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)
So how did my machine find llvm-g++ for $(LCXX) but the build machine found clang++?
Note i have configured my machine and pointed the test-suite at my bin folder as the command after that failing one has the correct path.
/Users/pete/svn...