llvm dev - Feb 2008 - [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:
>>> test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU]
>>
>> This test doesn't work with gcc-4.0, which caused it to fail on a
>> number of testers overnight.  I can fix that in 4.0, but as I
>> understand it we're going to drop support for it next release, so
how
>> about now?
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
> _______________________________________________
> llvm-testresults mailing list
> llvm-testresults at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-testresults

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 / 
Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C++Frontend/ 
2008-02-13-sret.cpp -o - | grep {retva\
l\|memtmp} | grep S242 |  grep {i32 1} | count 1
count: expected 1 lines and got        0.
child process exited abnormally

/usr/local/bin/llvm-gcc -v
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- 
transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-gxx-include-dir=/usr/ 
include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin9 -- 
enable-llvm=/usr/local --host=i686-apple-darwin9 --target=i686-apple- 
darwin9
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5546) (LLVM build 9999)

It's 4.2 based llvm-gcc.

Evan

On Feb 16, 2008, at 11:38 AM, Dale Johannesen wrote:
>
> 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:
>>>> test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU]
>>>
>>> This test doesn't work with gcc-4.0, which caused it to fail on
a
>>> number of testers overnight.  I can fix that in 4.0, but as I
>>> understand it we're going to drop support for it next release,
so
>>> how
>>> about now?
>>>
>>> _______________________________________________
>>> LLVM Developers mailing list
>>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>> _______________________________________________
>> llvm-testresults mailing list
>> llvm-testresults at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-testresults
>

>
> 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- 
> transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-gxx-include-dir=/usr/ 
> include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin9  
> --enable-llvm=/usr/local --host=i686-apple-darwin9 --target=i686- 
> apple-darwin9
> Thread model: posix
> gcc version 4.2.1 (Based on Apple Inc. build 5546) (LLVM build 9999)
>
> It's 4.2 based llvm-gcc.

Ok, so the gcc line on the tester web pages is worse than useless.

Works for me.  Make sure your llvm-gcc-4.2 is up to date, you need  
r47180.  The r46865 above suggests you might not have it.