From: scott snyder <snyder@d0sgif.fnal.gov>
To: law@cygnus.COM
Cc: egcs@cygnus.COM
Subject: Re: regression test results for 970904 on alpha-dec-osf4.0
Date: Thu, 04 Sep 1997 22:46:00 -0000 [thread overview]
Message-ID: <199709050546.FAA15859@d0sgif.fnal.gov> (raw)
In-Reply-To: <4795.873435911@hurl.cygnus.com>
> In message < 199709050447.EAA14961@d0sgif.fnal.gov >you write:
> > As reported earlier, this is due to assumption in this test case
> > that 2*sizeof(long) == sizeof(double), which is false for the alpha.
> > If this is fixed, this test passes.
>A patch would be welcome.
hi -
I included a little patch with the previous regression report i sent;
however, that was a little cheesy in that it tested for just __alpha.
Here's one which might be a little more generally applicable.
This still assumes that a double is 64 bits, but i'm not sure how
to reliably test for that using the preprocessor.
sss
*** /d0sgif/data1/snyder/egcs/gcc/testsuite/gcc.c-torture/execute/cbrt.c Mon Aug 25 11:37:23 1997
--- cbrt.c Fri Sep 5 01:37:58 1997
***************
*** 9,14 ****
--- 9,16 ----
* ====================================================
*/
+ #include <limits.h>
+
#ifndef __vax__
static const unsigned long
B1 = 715094163, /* B1 = (682-0.03306235651)*2**20 */
***************
*** 30,36 ****
--- 32,46 ----
unsigned sign;
union {
double t;
+ #ifndef WORD_BIT
+ unsigned long pt[2];
+ #elif (WORD_BIT == 32)
+ unsigned int pt[2];
+ #elif (LONG_BIT == 32)
unsigned long pt[2];
+ #else
+ #error No suitable integer type found.
+ #endif
} ut, ux;
int n0;
next prev parent reply other threads:[~1997-09-04 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-04 21:47 scott snyder
1997-09-04 22:05 ` Jeffrey A Law
1997-09-04 22:46 ` scott snyder [this message]
1997-09-04 22:58 ` Jeffrey A Law
1997-09-04 23:06 ` Richard Henderson
1997-09-04 23:20 ` Jeffrey A Law
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=199709050546.FAA15859@d0sgif.fnal.gov \
--to=snyder@d0sgif.fnal.gov \
--cc=egcs@cygnus.COM \
--cc=law@cygnus.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).