search for: featuretests

Hi! As I can see all nighttesters listed at http://llvm.cs.uiuc.edu/testresults/ have problem with FeatureTests at 2004-11-01/2004-11-02 test run. In my case i manualy terminate nighttest script after 12 hours work. It problem resolved? Vladimir

Vladimir Merzliakov wrote: > Hi! > > As I can see all nighttesters listed at > http://llvm.cs.uiuc.edu/testresults/ have problem with > FeatureTests at 2004-11-01/2004-11-02 test run. > > In my case i manualy terminate nighttest script after 12 hours work. > > It problem resolved? > > Vladimir Hi Vladimir, I assume you're talking about the FreeBSD run. I'm not sure what is going on there but other platforms have...

> Vladimir Merzliakov wrote: > >> Hi! >> >> As I can see all nighttesters listed at >> http://llvm.cs.uiuc.edu/testresults/ have problem with >> FeatureTests at 2004-11-01/2004-11-02 test run. >> >> In my case i manualy terminate nighttest script after 12 hours work. >> >> It problem resolved? >> >> Vladimir > > Hi Vladimir, > > I assume you're talking about the FreeBSD run. I'm not sure what is go...

...35343 0.0 1.7 11740 8820 ?? I 2:56AM 0:00.02 [python] make, ~/pkg/build/gcc > NightlyTest.pl run with -noremove and then i can send any generated file if need. Vladimir -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 2004-11-03-FeatureTests-Log.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041103/0a472f00/attachment.txt>

On Wed, 3 Nov 2004, Vladimir Merzliakov wrote: > >> It problem resolved? > >> > >> Vladimir > > > > Hi Vladimir, > > > > I assume you're talking about the FreeBSD run. I'm not sure what is going > > on > > No. You can see problem with Feature tests at > http://llvm.cs.uiuc.edu/testresults/X86/ also (see Feature Test Results

>> > I assume you're talking about the FreeBSD run. I'm not sure what is >> > going >> > on >> >> No. You can see problem with Feature tests at >> http://llvm.cs.uiuc.edu/testresults/X86/ also (see Feature Test Results >> section ) > > I'm not sure that I follow. The qmtest stuff isn't working on Zion > because (I

...[python] >> wanderer 35343 0.0 1.7 11740 8820 ?? I 2:56AM 0:00.02 >> [python] >> make, ~/pkg/build/gcc > >> >> NightlyTest.pl run with -noremove and then i can send any generated >> file if need. >> >> Vladimir >> <2004-11-03-FeatureTests- >> Log.txt>_______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev > > _______________________________________________ > LLVM D...

...?? I 2:56AM 0:00.57 > [python] > wanderer 35343 0.0 1.7 11740 8820 ?? I 2:56AM 0:00.02 > [python] > make, ~/pkg/build/gcc > > > NightlyTest.pl run with -noremove and then i can send any generated > file if need. > > Vladimir > <2004-11-03-FeatureTests- > Log.txt>_______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev

...0.0 1.7 11740 8820 ?? I 2:56AM 0:00.02 >>> [python] >>> make, ~/pkg/build/gcc > >>> >>> NightlyTest.pl run with -noremove and then i can send any generated >>> file if need. >>> >>> Vladimir >>> <2004-11-03-FeatureTests- >>> Log.txt>_______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> >> __________________________...

On Wed, 08 Dec 2010 12:09:27 -0600 greened at obbligato.org (David A. Greene) wrote: > Török Edwin <edwintorok at gmail.com> writes: > > > What are we left with then? Only 4.2 and 4.3? > > On SLES 10.1 at least. I think it is highly platform dependent. Also keep in mind that llvm-gcc uses the 4.2 unwinder, so if you are seeing EH failures maybe the EH info generated by

Török Edwin <edwintorok at gmail.com> writes: > What are we left with then? Only 4.2 and 4.3? On SLES 10.1 at least. I think it is highly platform dependent. > I only use 4.4 since a while, and it works fairly well. On what platform? > Are you sure it is not a bug in the regression tests themselves > (strict-aliasing bugs, etc.)? No, I'm not sure. > Which

Török Edwin <edwintorok at gmail.com> writes: >> > Which regression tests are failing with LLVM 2.8 and GCC 4.4.x? >> >> Too many to list. > > Can you give me 2 or 3 examples (that fail with LLVM 2.8 and GCC 4.4 > but work with LLVM 2.8 and GCC 4.3), also I'd like to know how they > fail. > If I have some time I'll check with my 4.4 to see if

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

For compiling the xen kernel we use -nostdinc which means we don''t want to rely on any external headers. That also counts vor stdarg.h. Use the external header when we compile the tools. Adapt libelf-loader.c which is compiled in the kernel and with the tools. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced