public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/13408] acats numeric tests cxg* fail on pa/hpux Date: Tue, 06 Jan 2004 18:10:00 -0000 [thread overview] Message-ID: <20040106181030.13619.qmail@sources.redhat.com> (raw) In-Reply-To: <20031216031240.13408.danglin@gcc.gnu.org> ------- Additional Comments From danglin at gcc dot gnu dot org 2004-01-06 18:10 ------- There's potentially two separate issues involved in this PR and 13528: 1) The float to integer conversion of an Inf which causes a SIGFPU and the termination of the acats test sequence. This is definitely a testsuite/ada problem. I don't have a copy of the IEEE spec handy but the PA-RISC 2.0 Architecture book indicates that an unimplemented exception is always signaled for this condition. 2) The failure of various cxg* tests (and some others) due to the error limit for the test being exceeded by a small amount. I suspect that the cxg* failures have been present on the hppa2.0w-hp-hpux11 port since the acats testsuite was installed. This report represented the first successful build of ada since the testsuite was installed. I could do a build just after the testsuite was installed to see if there was any regression from that time. I would have to backport Roger Sayle's loop.c patch. It resolved the miscompilation of gnat1 which prevented builds for a long time. The numeric failures don't occur on the hppa-linux port. Thus, I doubt the problem is directly in the GCC code. The primary differences between the two ports are: a) HP libc/libm versus glibc b) Long double on hppa-linux port is the same as double. Long double on hppa-hpux port uses HP "quadlib" routines in libc. c) Linux port has flat memory model and doesn't need to be built with -mdisable-indexing. `c' usually results in segmentation faults, so I doubt it is the problem. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13408
next prev parent reply other threads:[~2004-01-06 18:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-16 4:00 [Bug ada/13408] New: make: *** [check-gnat] Error 136 danglin at gcc dot gnu dot org 2003-12-16 4:08 ` [Bug ada/13408] " danglin at gcc dot gnu dot org 2003-12-16 10:03 ` charlet at act-europe dot fr 2004-01-06 14:41 ` [Bug ada/13408] acats numeric tests cxg* fail on pa/hpux charlet at gcc dot gnu dot org 2004-01-06 14:58 ` charlet at gcc dot gnu dot org 2004-01-06 18:10 ` danglin at gcc dot gnu dot org [this message] 2004-01-06 18:46 ` pinskia at gcc dot gnu dot org 2004-04-17 21:15 ` laurent at guerby dot net 2004-09-22 22:08 ` danglin at gcc dot gnu dot org [not found] <bug-13408-276@http.gcc.gnu.org/bugzilla/> 2005-10-12 19:47 ` laurent at guerby dot net 2005-10-12 19:58 ` dave at hiauly1 dot hia dot nrc dot ca
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=20040106181030.13619.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).