From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: remaining ppc problems
Date: Sun, 08 Jan 2006 06:32:00 -0000 [thread overview]
Message-ID: <43C0B205.9030802@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
I've seen for a long time now problems in test-fenv.
Test: after fesetenv (FE_NOMASK_ENV) processes will abort
when feraiseexcept (FE_DIVBYZERO) is called.
Fail: Process didn't receive signal and exited with status 512.
(several times)
Test: after fesetenv (FE_NOMASK_ENV) processes will abort
when feraiseexcept (FE_INVALID) is called.
Fail: Process didn't receive signal and exited with status 512.
(also several times)
Test: after fesetenv (FE_NOMASK_ENV) processes will abort
when feraiseexcept (FE_INEXACT) is called.
Fail: Process didn't receive signal and exited with status 512.
... you get the picture. Nobody else seeing this? It's a G5, it
happens in 32 and 64 bit mode, and it is 100% reproducible.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next reply other threads:[~2006-01-08 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 6:32 Ulrich Drepper [this message]
2006-01-08 6:58 ` Thorsten Kukuk
2006-01-13 17:58 ` Steven Munroe
2006-02-07 16:28 ` Steven Munroe
2006-02-07 18:00 ` Ulrich Drepper
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=43C0B205.9030802@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).