Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] nightly tester grawp"
2006 Dec 30
0
[LLVMdev] nightly tester grawp
Hi Devang,
Unfortunately, there's no way to see the build log unless you're on the
machine from which the report was generated. If you can log in to
Grawp's machine then it should be in the "WEBDIR".
It is most likely mis-compiling because the needed llvm-gcc patch has
not been applied after the SETCC patch to LLVM was committed last
weekend.
Reid.
On Fri, 2006-12-29 at
2006 Dec 30
2
[LLVMdev] nightly tester grawp
Reid,
Click on any of these logs and you'll see the same asm parsing
issues. It's been going on for much of the week.
http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt
http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt
llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build
(bytecode)
2006 Dec 30
0
[LLVMdev] nightly tester grawp
Jim Laskey wrote:
> llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build
> (bytecode)
> /Volumes/Muggles/LLVM/nightlytest/build/llvm/Release/bin/gccas: /
> Volumes/Muggles/LLVM/nightlytest/build/llvm/projects/Stacker/lib/
> runtime/Release/stacker_rt.ll:21,0: parse error, expecting `LOAD' or
> `STORE'
>
2006 Dec 30
3
[LLVMdev] nightly tester grawp
You all just need remove "stacker_rt.ll". the stacker_rt.ll is a
generated file, not source. The Makefile should have a dependency on
llvm-gcc for it, but doesn't. Just remove stacker_rt.ll and the problem
will go away.
Reid.
On Sat, 2006-12-30 at 08:37 -0500, Nick Lewycky wrote:
> Jim Laskey wrote:
> > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build
2006 Dec 31
3
[LLVMdev] nightly tester grawp
On Sun, 2006-12-31 at 13:37 -0800, Chris Lattner wrote:
> On Sat, 30 Dec 2006, Reid Spencer wrote:
> >>> You all just need remove "stacker_rt.ll". the stacker_rt.ll is a
> >> rebuilt so they output proper .ll files. Reid, can you change the
> >> makefile rule to use "llvm-gcc -S -emit-llvm -o - | llvm-upgrade > $@" or
> >> the
2007 Jan 01
0
[LLVMdev] nightly tester grawp
Ok, so I guess the issue is llvm-gcc has to be updated. There are
some issues with the Apple svn repository so I checked out a copy
from the public mirror. Looks the latest patch hasn't made it through:
c++ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -pedantic -Wno-long-
long -Wno-variadic-macros -mdynamic-no-pic -DHAVE_CONFIG_H -Wno-
unused
2006 Dec 30
2
[LLVMdev] nightly tester grawp
On Sat, 2006-12-30 at 11:53 -0800, Chris Lattner wrote:
> On Sat, 30 Dec 2006, Reid Spencer wrote:
> > You all just need remove "stacker_rt.ll". the stacker_rt.ll is a
> > generated file, not source. The Makefile should have a dependency on
> > llvm-gcc for it, but doesn't. Just remove stacker_rt.ll and the problem
> > will go away.
>
> This
2006 Dec 31
0
[LLVMdev] nightly tester grawp
On Sat, 30 Dec 2006, Reid Spencer wrote:
>>> You all just need remove "stacker_rt.ll". the stacker_rt.ll is a
>> rebuilt so they output proper .ll files. Reid, can you change the
>> makefile rule to use "llvm-gcc -S -emit-llvm -o - | llvm-upgrade > $@" or
>> the equivalent?
>
> Which makefile rule?
The rule in the stacker makefile that
2008 Feb 16
2
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 11:32 AM, Evan Cheng wrote:
> But I am using llvm-gcc-4.2. Any idea why it's failing?
>
> Evan
All the failing testers are using gcc-4.0 according to the web pages
they point at.
> On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote:
>
>> On Feb 16, 2008, at 7:06 AM, Apache wrote:
>>> New Test Failures:
>>>
2007 Jan 01
2
[LLVMdev] nightly tester grawp
On Mon, 2007-01-01 at 00:44 -0800, Evan Cheng wrote:
> Ok, so I guess the issue is llvm-gcc has to be updated. There are
> some issues with the Apple svn repository so I checked out a copy
> from the public mirror. Looks the latest patch hasn't made it through:
Yeah, it should have just made it througha couple hours ago, but not at
the time of your writing this email.
Reid.
2006 Dec 30
0
[LLVMdev] nightly tester grawp
On Sat, 30 Dec 2006, Reid Spencer wrote:
> You all just need remove "stacker_rt.ll". the stacker_rt.ll is a
> generated file, not source. The Makefile should have a dependency on
> llvm-gcc for it, but doesn't. Just remove stacker_rt.ll and the problem
> will go away.
This presumably doesn't impact the testers, as they start from a clean
build every night. The
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 /
2004 Jun 24
3
[LLVMdev] Using -noexternals option of NightlyTest.pl
At this moment I use
"gmake TEST=nightly" command line to run night tester
What I must specific and where to disable SPEC run (i don't have it)
I known about new NightlyTest.pl option: -noexternals
But what I must do for enable it
Vladimir
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Thu, 24 Jun 2004, Vladimir Merzliakov wrote:
> At this moment I use
> "gmake TEST=nightly" command line to run night tester
>
> What I must specific and where to disable SPEC run (i don't have it)
I think that it's currently a bug that this does not automatically happen.
> I known about new NightlyTest.pl option: -noexternals
> But what I must do for
2006 Feb 28
1
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
Reid Spencer wrote:
> On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote:
>
>>> Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld.
>>>
>> This didn't work for me:
>> llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a
>>
>> I get two warning's about library 'crtend' missing
2006 Feb 28
0
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote:
> > Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld.
> This didn't work for me:
> llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a
>
> I get two warning's about library 'crtend' missing
>
You didn't get the instructions quite right. The option is
2004 Jun 24
5
[LLVMdev] Using -noexternals option of NightlyTest.pl
> Are you using the NightlyTest.pl file? To run the tester I don't use
> gmake directly at all. Instead, I have this in my crontab:
>
> 5 3 * * *
LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs
$HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan
/home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86
>
> When run like this,
2004 Dec 26
1
[LLVMdev] README: Build Environment Changes
Next problem detected by nighttest:
LLVM build fail with errors:
gmake[4]: Entering directory
`/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime'
llvm[4]: Compiling stacker_rt.c for Debug build (bytecode)
default/bin/llvm-gcc: not found
gmake[4]: ***
[/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime/Debug/stacker_rt.bc]
Error 1
2006 Feb 28
3
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
Chris Lattner wrote:
> On Sun, 26 Feb 2006, Wink Saville wrote:
>> I then do the following in my makefile:
>>
>> llvm-gcc -c t1.c -o t1.bc
>> llvm-gcc -c t1sub1.c -o t1sub1.bc
>> llvm-gcc -c t1sub2.c -o t1sub2.bc
>> llvm-ar r t1.a t1sub1.bc t1sub2.bc
>> llvm-ar: creating t1.a
>> llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a
2008 Jan 10
4
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
Török Edwin wrote:
> Yes, I have uploaded the .tar.gz here:
> http://edwintorok.googlepages.com/ClamAV-srcflat.tar.gz
> [inputs dir contains some symlink, place ClamAV dir in
> llvm/projects/llvm-test/MultiSource/Applications to make
> links point to right place]
>
>
Hi,
Because llvm bug #1730 got fixed, this testcase can run under with the
JIT on x86-64 :).
I have