Displaying 20 results from an estimated 20 matches for "target_flag".
Did you mean:
targetflag
2008 Mar 21
0
[LLVMdev] Apple's GCC and .s/.S files in llvm-test
...assembler-with-cpp).
+FORCEASM =
+ifeq ($(OS),Darwin)
+FORCEASM = -x assembler
+endif
+
# Assemble (and link) an LLVM-linked program using the system assembler...
#
$(PROGRAMS_TO_TEST:%=Output/%.llc): \
Output/%.llc: Output/%.llc.s
- -$(LLVMGCCLD) $< -o $@ $(LLCLIBS) $(LLCASSEMBLERFLAGS) $(TARGET_FLAGS) $(LDFLAGS)
+ -$(LLVMGCCLD) $(FORCEASM) $< -o $@ $(LLCLIBS) $(LLCASSEMBLERFLAGS) \
+ $(TARGET_FLAGS) $(LDFLAGS)
$(PROGRAMS_TO_TEST:%=Output/%.llc-beta): \
Output/%.llc-beta: Output/%.llc-beta.s
- -$(LLVMGCCLD) $< -o $@ $(LLCLIBS) $(LLCASSEMBLERFLAGS) $(TARGET_FLAGS) $(LDFLAGS)
+ -$(LLVM...
2013 Jun 07
0
[LLVMdev] tools build issue with lnt in cross platform testing
The issues seems to be this line in the tools Makefile
timeit-target: timeit.c
$(LD_ENV_OVERRIDES) $(LCC) -o $@ $< $(LDFLAGS) $(CFLAGS)
$(TARGET_FLAGS) -O3
It should not add target flags if we are simulating the target on the host.
On 06/06/2013 06:59 PM, reed kotler wrote:
> I want to get lnt to use qemu for the execution.
>
> In that case, RHOST= is not set.
>
> But I change the Arch because I am going to run in cross mode....
2013 Jun 07
2
[LLVMdev] tools build issue with lnt in cross platform testing
I want to get lnt to use qemu for the execution.
In that case, RHOST= is not set.
But I change the Arch because I am going to run in cross mode.
Then I'm setting RUNUNDER to be a script which runs qemu.
In this case it builds timeit-target as a Mips which fails because this
is running on x86.
~/mysandbox/bin/lnt runtest nt --sandbox ~/mysandbox --cc
/local/llvmpb_a/install/bin/clang
2005 Jan 03
0
[LLVMdev] [patch] native AMD64 support
...error ("-malign-double makes no sense in the 64bit mode");
> if (TARGET_RTD)
> error ("-mrtd calling convention not supported in the 64bit mode");
> +#if EMIT_LLVM
> + /* set to standard X86 values (using 64-bit long doubles under LLVM) */
> + target_flags &= ~(MASK_SSE2 | MASK_SSE | MASK_MMX | MASK_128BIT_LONG_DOUBLE);
> + ix86_fpmath = FPMATH_387;
> +#else
> /* Enable by default the SSE and MMX builtins. */
> target_flags |= (MASK_SSE2 | MASK_SSE | MASK_MMX | MASK_128BIT_LONG_DOUBLE);
> ix86_fpmath = F...
2012 Nov 15
1
[LLVMdev] Unit tests - ARM
I use variants on the following command:
make -k TEST=simple ARCH=ARM TARGET_FLAGS="-arch armv7 -isysroot path-to-sdk -ccc-install-dir path-to-binutils" USE_REFERENCE_OUTPUT=1 REMOTE_HOST=localhost REMOTE_USER=root REMOTE_CLIENT=ssh REMOTE_PORT=10022 DISABLE_JIT=1 DISABLE_CBE=1 SMALL_PROBLEM_SIZE=1 TARGET_CC=path-to-clang TARGET_CXX=path-to-clang++ report
That assumes...
2012 Sep 06
2
[LLVMdev] LNT: failing to parse compiler info: what am I doing wrong?
...test_instance.run_test('%s %s' % (name, test_name), args)
File "/home/sean/pg/others/llvm/lnt/lnt/tests/nt.py", line 1288, in run_test
report = run_test(nick, opts, None, report_dir)
File "/home/sean/pg/others/llvm/lnt/lnt/tests/nt.py", line 645, in run_test
target_flags)
File "/home/sean/pg/others/llvm/lnt/lnt/testing/util/compilers.py",
line 82, in get_cc_info
cc_name,cc_version_num,cc_build_string,cc_extra = m.groups()
AttributeError: 'NoneType' object has no attribute 'groups'
I took a look at the code and basically it's do...
2011 Jul 28
0
[LLVMdev] LLVM / CLANG Test Infrastructure Question
...GET_IS_X86_64=1 DISABLE_CBE=1 DISABLE_JIT=1 ENABLE_HASHED_PROGRAM_OUTPUT=1 ENABLE_OPTIMIZED=1 LD_ENV_OVERRIDES="env DYLD_LIBRARY_PATH=/path/to/your/build/Release+Asserts/lib" LLC_OPTFLAGS=-O3 LLI_OPTFLAGS=-O3 OPTFLAGS=-O3 SMALL_PROBLEM_SIZE=1 TARGET_CC="" TARGET_CXX="" TARGET_FLAGS="-arch x86_64" TARGET_LLVMGCC=/path/to/your/build/Release+Asserts/bin/clang TARGET_LLVMGXX=/path/to/your/build/Release+Asserts/bin/clang++ TEST=simple USE_REFERENCE_OUTPUT=1 report
***Note the ENABLE_OPTIMIZED=1 flag requires that you run configure with '--enable-optimized' at c...
2011 Jul 28
2
[LLVMdev] LLVM / CLANG Test Infrastructure Question
> > 1. I checked out and built llvm, clang, and test-suite from svn tip.
> When I
> > run llvm/test *without* my changes on x86, I see 3 failures. Is it
> expected?
> > I was expecting svn tip on x86 to be clean. Is there a nightly
> regression
> > result available somewhere that I can check for broken tests. Here is
> the
> > report from my log:
> >
2012 Sep 06
0
[LLVMdev] LNT: failing to parse compiler info: what am I doing wrong?
...est('%s %s' % (name, test_name), args)
> File "/home/sean/pg/others/llvm/lnt/lnt/tests/nt.py", line 1288, in run_test
> report = run_test(nick, opts, None, report_dir)
> File "/home/sean/pg/others/llvm/lnt/lnt/tests/nt.py", line 645, in run_test
> target_flags)
> File "/home/sean/pg/others/llvm/lnt/lnt/testing/util/compilers.py",
> line 82, in get_cc_info
> cc_name,cc_version_num,cc_build_string,cc_extra = m.groups()
> AttributeError: 'NoneType' object has no attribute 'groups'
>
> I took a look at the c...
2010 Mar 12
0
[LLVMdev] Let's -disable-post-ra for x86
Hi Jakob,
It's not completely clear from your post, I think your chart is just
for x86_64? What does it look like for x86_32?
- Daniel
On Thu, Mar 11, 2010 at 4:58 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote:
> We are currently running the post-ra scheduler for x86 with -O3. It is not really clear that it is worth the compile time.
>
> X86 scheduling is a mystery
2012 Nov 15
0
[LLVMdev] Unit tests - ARM
Hi Raul,
I've successfully run them over ssh using LNT without too much
difficulty. There is documentation on getting started with the LNT
system here: http://llvm.org/docs/lnt/quickstart.html.
It doesn't specifically mention remote execution, but if you give the
lnt command a "--help" option then there are a few reasonably
self-explanatory options described (--remote,
2013 Mar 12
0
[LLVMdev] LNT BenchmarkGame
...olin/devel/llvm/build/bin/clang" "TARGET_CXX=None"
"LLI_OPTFLAGS=-O3" "TARGET_CC=None"
"TARGET_LLVMGXX=/home/rengolin/devel/llvm/build/bin/clang++" "TEST=simple"
"CC_UNDER_TEST_IS_CLANG=1" "ENABLE_PARALLEL_REPORT=1" "TARGET_FLAGS="
"USE_REFERENCE_OUTPUT=1" "CC_UNDER_TEST_TARGET_IS_X86_64=1" "OPTFLAGS=-O3"
"LLC_OPTFLAGS=-O3" "ENABLE_OPTIMIZED=1" "ARCH=x86_64"
"ENABLE_HASHED_PROGRAM_OUTPUT=1" "DISABLE_JIT=1" "-C"
"SingleSo...
2007 May 04
0
[LLVMdev] llvm-test make problems
On Fri, 4 May 2007, Florian Brandner wrote:
> make[1]: Leaving directory `/localtmp/brandner/dev/llvm-test/SingleSource'
> make: *** [SingleSource/.maketest] Error 2
Is it just this one test that doesn't work, or do no tests work? If no
tests work, you probably need to rerun configure in llvm-test. Make sure
that llvm-gcc is in your path and detected by the configure script.
2012 Sep 06
1
[LLVMdev] LNT: failing to parse compiler info: what am I doing wrong?
...39; % (name, test_name), args)
>> File "/home/sean/pg/others/llvm/lnt/lnt/tests/nt.py", line 1288, in run_test
>> report = run_test(nick, opts, None, report_dir)
>> File "/home/sean/pg/others/llvm/lnt/lnt/tests/nt.py", line 645, in run_test
>> target_flags)
>> File "/home/sean/pg/others/llvm/lnt/lnt/testing/util/compilers.py",
>> line 82, in get_cc_info
>> cc_name,cc_version_num,cc_build_string,cc_extra = m.groups()
>> AttributeError: 'NoneType' object has no attribute 'groups'
>>
>>...
2008 Jun 03
3
[LLVMdev] Linux x86 testers needed!
> I had planned to try again once 2.3 is out, but if you're short on Linux
> testers, I'll join in.
>
> Available platforms:
> * x86_64
> * i686 compatibility
> Given that I had problems getting the latter to run, I think I should
> concentrate on x86_64.
> Should I switch PIC off for that?
Thanks! Running a linux tester would be a huge help for the project.
2013 Mar 12
2
[LLVMdev] LNT BenchmarkGame
On 12 March 2013 16:21, Duncan Sands <baldrick at free.fr> wrote:
> IIRC the reference output is not used by default. You have to put
> USE_REFERENCE_OUTPUT := 1
> in the Makefile in order to make use of the reference output. As
> BenchmarkGame doesn't have this, are you sure the reference output
> is causing the problem?
>
That was my initial assumption, too. But
2010 Mar 12
3
[LLVMdev] Let's -disable-post-ra for x86
We are currently running the post-ra scheduler for x86 with -O3. It is not really clear that it is worth the compile time.
X86 scheduling is a mystery that post-ra has not solved.
I ran the nightly test suite on x86_64 with LTO enabled and -O3 with and without -disable-post-ra. Code generation is 10% faster overall with -disable-post-ra, and the runtime impact varies from a 17% speedup to a 17
2012 Nov 15
4
[LLVMdev] Unit tests - ARM
Hello,
is there any option to run LLVM unit tests on ARM from your desktop? I
mean, the code is properly cross-compiled on your desktop and you want to
run the unit tests automatically on an ARM board. Chrood might work, but I
am looking for some option like <runremote.sh --host XXX --user ....>. I
have seen something related to it in projects/test-suite/Makefile.programs
(REMOTE_HOST,
2007 May 04
3
[LLVMdev] llvm-test make problems
Reid Spencer wrote:
> Have you modified the makefile in any way? Note that sse.expantfft.bc should be sse.expandfft.bc
no, did'nt change it.
the typo before seems to be an error while copying from the terminal.
i've cleaned everything and tried again. this is the messsage:
[brandner:/localtmp/brandner/dev/llvm-test:529] make -j1 TEST=nightly
2>&1 | tee report.nightly.raw.out
2014 May 16
5
[LLVMdev] Use perf tool for more accurate time measuring on Linux
.../Makefile (working copy)
@@ -8,8 +8,13 @@
all:: timeit-target
endif
+ifeq ($(TARGET_OS),Linux)
+timeit: timeit.sh
+ cp -f $< $@
+else
timeit: timeit.c
$(ORIGINAL_CC) $(CFLAGS) -O3 -o $@ $<
+endif
timeit-target: timeit.c
$(LD_ENV_OVERRIDES) $(LCC) -o $@ $< $(LDFLAGS) $(CFLAGS) $(TARGET_FLAGS) -O3