public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david dot kirkby at onetel dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/40757] gcc 4.4.0 miscompiles mpfr-2.4.1
Date: Thu, 16 Jul 2009 10:19:00 -0000 [thread overview]
Message-ID: <20090716101910.6784.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40757-16207@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from david dot kirkby at onetel dot net 2009-07-16 10:19 -------
(In reply to comment #4)
> mpfr-2.4.1 compiles and tests Ok for me on an Ultra5 (USIIi) running
> sparc64-linux, with gmp-4.2.4 (compiled by gcc-4.3.4) and gcc 4.3.4, 4.4.0, and
> 4.4.1 20090630.
>
> I don't have a T2, but could possibly do some tests on USIIIi/Solaris 9.
>
I believe the problem is likely to only be seen on the T2+ or similar
processors. Someone noticed the library code in OpenSolaris is different on the
T2+ processor to what it would be on a more common SPARC processor.
I have built gcc 4.4.0 on Solaris 10 on a Sun Blade 2000 (UltraSPARC II
processors) and have no problem with mpfr, but on the T2+ processors of the
T5240 server, it does not work.
I'll try a later snapshot, but any serious gcc developer would be welcome to an
account on the machine where it fails. That does not mean anyone that just
happens to be interested and fancies playing on a 16-core machine, but if you
are a serious gcc developer, then I could give you an account.
Dave
--
david dot kirkby at onetel dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |david dot kirkby at onetel
| |dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40757
next prev parent reply other threads:[~2009-07-16 10:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 0:36 [Bug c/40757] New: " zimmerma+gcc at loria dot fr
2009-07-15 2:02 ` [Bug c/40757] " zimmerma+gcc at loria dot fr
2009-07-15 6:27 ` ebotcazou at gcc dot gnu dot org
2009-07-15 9:55 ` rguenth at gcc dot gnu dot org
2009-07-15 13:15 ` mikpe at it dot uu dot se
2009-07-16 7:52 ` zimmerma+gcc at loria dot fr
2009-07-16 8:31 ` mikpe at it dot uu dot se
2009-07-16 10:19 ` david dot kirkby at onetel dot net [this message]
2009-07-16 10:24 ` david dot kirkby at onetel dot net
2009-07-16 10:31 ` jakub at gcc dot gnu dot org
2009-07-16 12:32 ` david dot kirkby at onetel dot net
2009-07-16 14:07 ` jakub at gcc dot gnu dot org
2009-07-16 20:34 ` marc dot glisse at normalesup dot org
2009-07-16 21:29 ` david dot kirkby at onetel dot net
2009-07-17 0:58 ` zimmerma+gcc at loria dot fr
2009-07-17 3:22 ` david dot kirkby at onetel dot net
2009-07-17 4:11 ` david dot kirkby at onetel dot net
2009-07-17 7:49 ` jakub at gcc dot gnu dot org
2009-07-17 11:19 ` david dot kirkby at onetel dot net
2009-07-17 15:51 ` marc dot glisse at normalesup dot org
2009-07-18 1:14 ` david dot kirkby at onetel dot net
2009-07-18 1:18 ` david dot kirkby at onetel dot net
2009-07-18 4:50 ` marc dot glisse at normalesup dot org
2009-07-18 14:36 ` david dot kirkby at onetel dot net
2009-07-18 14:44 ` david dot kirkby at onetel dot net
2009-07-18 19:33 ` david dot kirkby at onetel dot net
2009-10-01 8:34 ` [Bug target/40757] " david dot kirkby at onetel dot net
2009-10-04 11:01 ` ebotcazou at gcc dot gnu dot org
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=20090716101910.6784.qmail@sourceware.org \
--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: 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).