From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] glibc/gcc bug -> perl/gcc bug?
Date: Sun, 30 Mar 2003 21:32:40 -0500 [thread overview]
Message-ID: <20030331023240.GB23960@systemhalted> (raw)
In-Reply-To: <20030331003153.GS11333@tausq.org>
> perl-5.8 fails to build on hppa because of a test failure. The problem
> can be seen very easily:
>
> tausq@gsyprf11:~/build/perl-5.8.0$ cat t/t.pl
> print log "A";
> tausq@gsyprf11:~/build/perl-5.8.0$ ./perl t/t.pl
> Can't take log of 2.75773e-308 at t/t.pl line 1.
>
> that should have said:
> tausq@gsyprf11:~/build/perl-5.8.0$ /usr/bin/perl t/t.pl
> Can't take log of 0 at t/t.pl line 1.
>
> interestingly, a debug build of perl (using -g and no -O flags) doesn't
> have the same problem, so this looks like some kind of compiler
> optimization bug. I've tried this with both 3.2.3 and 3.3... same
> problems.
>
> would anyone like to try to look at this some more and see if they can
> isolate the C code/a small test case that is causing the problem?
Glibc's math tests are still failing even under gcc-3.3 (not to mention
the threading problems I'm in the middle of fixing).
Though I'm seeing more:
Failure: Real part of: cacos (NaN + inf i) == NaN - inf i: Exception "Invalid operation" set
Failure: Real part of: cacos (NaN - inf i) == NaN + inf i: Exception "Invalid operation" set
Failure: Real part of: cacos (NaN + NaN i) == NaN + NaN i: Exception "Invalid operation" set
Or:
Failure: Test: Imaginary part of: ctanh (NaN - 0 i) == NaN - 0 i
Result:
is: nan nan
should be: -0.00000000000000000000e+00 -0x0.00000000000000000000p+0
Even with a new ulps, the tests were still failing.
c.
prev parent reply other threads:[~2003-03-31 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 0:31 [parisc-linux] perl/gcc bug if someone wants to look :) Randolph Chung
2003-03-31 2:32 ` Carlos O'Donell [this message]
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=20030331023240.GB23960@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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