search for: negativezero

Chris Lattner wrote: > Specifically which test is this? It is possible we can just change the > test to not depend on this. Assembler/2004-02-01-NegativeZero.ll ; RUN: llvm-as < %s | llvm-dis | grep -- -0.0 global double 0x8000000000000000 global float -0.0 The .bc made by both Linux and OpenBSD is identical according to an md5 hash.

On Tue, 1 Jul 2008, Edd Barrett wrote: >> as much information as you can provide since it may not be a target that >> the majority of the developers have access to. > > The target is OpenBSD/i386 for now and later sparc64 and amd64. Most of Ok, that sounds like we need to increase testsuite portability. > the errors are to do with GNU grep syntax not being compatible with

On Tue, 1 Jul 2008, Edd Barrett wrote: > Chris Lattner wrote: >> Specifically which test is this? It is possible we can just change the >> test to not depend on this. > > Assembler/2004-02-01-NegativeZero.ll > > ; RUN: llvm-as < %s | llvm-dis | grep -- -0.0 > > global double 0x8000000000000000 > global float -0.0 > > The .bc made by both Linux and OpenBSD is identical according to an md5 > hash. If the output of llvm-dis is "0.0" instead of "-0.0", the...

...r benchmarking purposes. Here are some examples: http://llvm.cs.uiuc.edu/cvsweb/cvsweb.cgi/llvm/test/Programs/SingleSource/UnitTests/2003-05-31-CastToBool.c?rev=1.3&content-type=text/x-cvsweb-markup http://llvm.cs.uiuc.edu/cvsweb/cvsweb.cgi/llvm/test/Programs/SingleSource/UnitTests/2004-02-02-NegativeZero.c?rev=1.1&content-type=text/x-cvsweb-markup Doing more performance tuning is certainly important though, it's just that other projects have taken priority. There are *so* many good things that can be done in a compiler, especially in one as multifaceted as LLVM. :) > > What is wron...

...he tree. The second one is Transforms/SimplifyLibCalls/floor.ll. nearbyint is not replaced by nearbyintf since neither function is defined in the OpenBSD libm. The other two are replaced fine though. My crude solution was to remove checking for nearbyintf. The third one is Assembler/2004-02-01-NegativeZero.ll. This fails because the constants are printed as positive zeros. I know there is a bug in libc on OpenBSD 4.3 that makes it print negative zeros as positive. It will be fixed in the next release and if this is linked then there is no concern. Arnaud -------------- next part -------------- A...

> The nightly tester is used for two purposes: making sure that nothing > breaks (the unit tests) and keeping tabs on how well performance is doing > (the spec and most multisource tests). It's not a reliable way to do > serious benchmarking, but can give good insights into where things can be > improved. hm, one day, the great benchmarking will be a reason to use LLVM, so, i

...ource/UnitTests/2003-08-05-CastFPToUint SingleSource/UnitTests/2003-08-11-VaListArg SingleSource/UnitTests/2003-08-20-FoldBug SingleSource/UnitTests/2003-09-18-BitFieldTest SingleSource/UnitTests/2003-10-13-SwitchTest SingleSource/UnitTests/2003-10-29-ScalarReplBug SingleSource/UnitTests/2004-02-02-NegativeZero SingleSource/UnitTests/2004-06-20-StaticBitfieldInit SingleSource/UnitTests/2004-11-28-GlobalBoolLayout SingleSource/UnitTests/2005-05-11-Popcount-ffs-fls SingleSource/UnitTests/2005-05-12-Int64ToFP SingleSource/UnitTests/2005-05-13-SDivTwo SingleSource/UnitTests/2005-07-17-INT-To-FP SingleSource/U...

Hi, Tanya M. Lattner wrote: >> We were wondering if *all* of the dejagnu tests should pass (in the >> sense that no result should be unexpected), because we have a few failed >> tests on our build. > > make check should always be clean. However, sometimes people do commit > changes that impact platforms they are not able to test on and we do have > the occasional

...ce/UnitTests/block-byref-test | * | * | SingleSource/UnitTests/conditional-gnu-ext-cxx | * | * | SingleSource/UnitTests/2003-07-09-SignedArgs | * | * | SingleSource/UnitTests/2004-02-02-NegativeZero | * | * | SingleSource/UnitTests/2005-05-13-SDivTwo | * | * | SingleSource/UnitTests/StructModifyTest | * | * | SingleSource/UnitTests/stmtexpr...

...* 0.00 | - - n/a n/a SingleSource/UnitTests/2003-10-29-ScalarReplBug | 0.0035 532 0.0019 * 0.0021 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/UnitTests/2004-02-02-NegativeZero | 0.0026 616 0.0027 * 0.0026 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/UnitTests/2004-06-20-StaticBitfieldInit | 0.0023 572 0.0020 * 0.0020 |...

...* 0.01 | - - n/a n/a SingleSource/UnitTests/2003-10-29-ScalarReplBug | 0.0000 532 0.0000 * 0.0040 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/UnitTests/2004-02-02-NegativeZero | 0.0040 600 0.0040 * 0.0040 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/UnitTests/2004-06-20-StaticBitfieldInit | 0.0000 632 0.0000 * 0.0040 |...

LLVMers, The 2.2 prerelease is now available for testing: http://llvm.org/prereleases/2.2/ If anyone can help test this release, I ask that you do the following: 1) Build llvm and llvm-gcc (or use a binary). You may build release (default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both. 2) Run 'make check'. 3) In llvm-test, run 'make TEST=nightly report'. 4) When

...* 0.01 | - - n/a n/a SingleSource/UnitTests/2003-10-29-ScalarReplBug | 0.0069 524 0.0015 * 0.0058 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/UnitTests/2004-02-02-NegativeZero | 0.0032 612 0.0065 * 0.0081 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/UnitTests/2004-06-20-StaticBitfieldInit | 0.0051 624 0.0018 * 0.0018 |...

...* 0.00 | - - n/a n/a SingleSource/UnitTests/2003-10-29-ScalarReplBug | 0.0015 556 0.0010 * 0.0009 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/UnitTests/2004-02-02-NegativeZero | 0.0011 644 0.0016 * 0.0015 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/UnitTests/2004-06-20-StaticBitfieldInit | 0.0009 596 0.0010 * 0.0010 |...

...01 | -       -       n/a          n/a > SingleSource/UnitTests/2003-10-29-ScalarReplBug                          | > 0.0000 580      0.0000      *                0.0000      |    0.00    0.00 >  0.00 *           0.01 | -       -       n/a          n/a > SingleSource/UnitTests/2004-02-02-NegativeZero                           | > 0.0000 640      0.0000      *                0.0000      |    0.00    0.00 >  0.00 *           0.01 | -       -       n/a          n/a > SingleSource/UnitTests/2004-06-20-StaticBitfieldInit                     | > 0.0000 684      0.0000      *              ...

Hi Tanya, > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. I compiled llvm and llvm-gcc with separate objects directories. Platform is x86_64-linux-gnu. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to

...n/a n/a > SingleSource/UnitTests/2003-10-29- > ScalarReplBug | 0.0000 580 0.0000 > * 0.0000 | 0.00 0.00 0.00 * > 0.01 | - - n/a n/a > SingleSource/UnitTests/2004-02-02- > NegativeZero | 0.0000 640 0.0000 > * 0.0000 | 0.00 0.00 0.00 * > 0.01 | - - n/a n/a > SingleSource/UnitTests/2004-06-20- > StaticBitfieldInit | 0.0000 684 0.0000 >...

LLVMers, The 2.1 pre-release (version 1) is available for testing: http://llvm.org/prereleases/2.1/version1/ I'm looking for members of the LLVM community to test the 2.1 release. There are 2 ways you can help: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

LLVMers, The 2.5 pre-release is available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run "make