From: Carlos O'Donell <carlos@systemhalted.org>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
Randolph Chung <tausq@debian.org>,
parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression).
Date: Fri, 15 Jul 2005 19:44:48 -0400 [thread overview]
Message-ID: <20050715234448.GA5314@systemhalted.org> (raw)
In-Reply-To: <20050715142609.GR5314@systemhalted.org>
On Fri, Jul 15, 2005 at 10:26:10AM -0400, Carlos O'Donell wrote:
> make[2]: *** [/glibc/math/test-fenv.out] Error 1
> = Regression (1)
> make[2]: *** [/glibc/math/test-float.out] Error 1
> make[2]: *** [/glibc/math/test-double.out] Error 1
> make[2]: *** [/glibc/math/test-ifloat.out] Error 1
> make[2]: *** [/glibc/math/test-idouble.out] Error 1
> make[1]: *** [math/tests] Error 2
> make[2]: *** [/glibc/stdlib/tst-strtod.out] Error 1
> make[2]: *** [/glibc/stdlib/bug-strtod.out] Error 1
> make[1]: *** [stdlib/tests] Error 2
> make[2]: [/glibc/posix/annexc.out] Error 1 (ignored)
> make[2]: *** [/glibc/elf/tst-array1.out] Error 1
> make[2]: *** [/glibc/elf/tst-array2.out] Error 1
> make[2]: *** [/glibc/elf/tst-array3.out] Error 1
> make[2]: *** [/glibc/elf/tst-array4.out] Error 1
> make[2]: *** [/glibc/elf/tst-array1-static.out] Error 1
> = Regressions (5)
> make[2]: *** [/glibc/elf/tst-tls13.out] Error 1
> = TIMEOUTFACTOR=10 required.
> make[1]: *** [elf/tests] Error 2
> make: *** [check] Error 2
Fixed binutils...
Make that 1 regression:
make[2]: *** [/glibc/math/test-fenv.out] Error 1
make[2]: *** [/glibc/math/test-float.out] Error 1
make[2]: *** [/glibc/math/test-double.out] Error 1
make[2]: *** [/glibc/math/test-ifloat.out] Error 1
make[2]: *** [/glibc/math/test-idouble.out] Error 1
make[1]: *** [math/tests] Error 2
make[2]: *** [/glibc/stdlib/tst-strtod.out] Error 1
make[2]: *** [/glibc/stdlib/bug-strtod.out] Error 1
make[1]: *** [stdlib/tests] Error 2
make[2]: [/glibc/posix/annexc.out] Error 1 (ignored)
make: *** [check] Error 2
However, the following is troubling and where trouble goes, so does the
blame on the compiler.
test-float.out (Non-inline float):
Test suite completed:
2599 test cases plus 2384 tests for exception flags executed.
- 39 errors occurred.
+ 4363 errors occurred.
test-double.out (Non-inline double):
Test suite completed:
2624 test cases plus 2399 tests for exception flags executed.
- 38 errors occurred.
+ 4388 errors occurred.
Although the numbers don't add up with the errors a cursory check shows
*none* of the non-inline math tests passed.
The inline math does *much* better, observe:
test-ifloat.out (Inline float):
Test suite completed:
2537 test cases plus 2322 tests for exception flags executed.
- 1 errors occurred.
+ 11 errors occurred.
test-idbouble.out (Inline double):
Test suite completed:
2562 test cases plus 2337 tests for exception flags executed.
- 1 errors occurred.
+ 10 errors occurred.
c.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-07-15 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 14:26 [parisc-linux] TLS toolchain update (6 regressions left) Carlos O'Donell
2005-07-15 23:44 ` Carlos O'Donell [this message]
2005-07-16 0:08 ` [parisc-linux] Re: Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression) John David Anglin
2005-07-16 0:57 ` Carlos O'Donell
2005-07-16 1:14 ` Carlos O'Donell
2005-07-16 1:54 ` John David Anglin
2005-07-16 18:38 ` Carlos O'Donell
2005-07-16 19:15 ` John David Anglin
2005-07-16 19:16 ` Carlos O'Donell
2005-07-16 19:48 ` John David Anglin
2005-07-16 20:13 ` Carlos O'Donell
2005-07-16 20:29 ` John David Anglin
2005-07-16 21:18 ` Carlos O'Donell
2005-07-16 22:55 ` John David Anglin
2005-07-17 16:21 ` [parisc-linux] TLS toolchain update (6 regressions left) Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050715234448.GA5314@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox