From: Carlos O'Donell <carlos@systemhalted.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org, tausq@debian.org
Subject: [parisc-linux] Re: Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression).
Date: Fri, 15 Jul 2005 20:57:15 -0400 [thread overview]
Message-ID: <20050716005715.GC5314@systemhalted.org> (raw)
In-Reply-To: <200507160008.j6G08hdg005634@hiauly1.hia.nrc.ca>
On Fri, Jul 15, 2005 at 08:08:43PM -0400, John David Anglin wrote:
> > 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.
>
> I don't want to throw stones but I posted a message to parisc two
> days ago indicating that we have at least one kernel bug in its math
> emulation ;)
I knew I'd draw you ire if I blamed the compiler! :)
> Ok, PA 2.0 support could be suspect. I doubt very much there are
> major FP issues with PA 1.1. In PA 1.1, essentially all the operations
> are supported in hardware (I hate assist). There's an issue with
> complex support using PA 1.0 but if the compiler didn't die that's
> not likely the problem. That's fixed in main. Finally, you've got
> the glibc issue in handling 64-bit long doubles. I would suspect a
> glibc issue first. GCC doesn't have much to do with exception support
> or control of rounding modes, although you would think the compiler
> would need to know about rounding mode.
I'm only testing float and double support, I have temporarily disabled
long double support for hppa during testing.
I don't quite understand how something like "fpclassify" can *ever* fail
under any implementation.
Could you review these files:
http://cvs.parisc-linux.org/glibc/sysdeps/hppa/fpu/
With an eye to correct asm statement? If these don't work then it all
goes down the tubes. I'm sure gcc is probably doing the right thing and
that asm is doing the wrong thing.
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-16 0:57 UTC|newest]
Thread overview: 22+ 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 ` [parisc-linux] Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression) Carlos O'Donell
2005-07-16 0:08 ` [parisc-linux] " John David Anglin
2005-07-16 0:57 ` Carlos O'Donell [this message]
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
[not found] <no.id>
2005-07-16 2:55 ` [parisc-linux] Re: Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression) John David Anglin
2005-07-16 16:16 ` Carlos O'Donell
2005-07-16 17:37 ` John David Anglin
2005-07-16 17:54 ` John David Anglin
2005-07-16 19:41 ` Carlos O'Donell
2005-07-16 19:56 ` John David Anglin
2005-07-16 19:15 ` 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=20050716005715.GC5314@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.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