From: Andrew Haley <aph@redhat.com>
To: Jean Christophe Beyler <jean.christophe.beyler@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GMP and GCC 4.3.2
Date: Thu, 17 Dec 2009 10:27:00 -0000 [thread overview]
Message-ID: <4B2A0791.7080509@redhat.com> (raw)
In-Reply-To: <c568a2600912161050v45f2322ay59c74d88299d1d91@mail.gmail.com>
Jean Christophe Beyler wrote:
> Dear all,
>
> Found on http://gmplib.org/.
>
> "N.B. gcc 4.3.2 miscompiles GMP 4.3.x on 64-bit machines. The problem
> is specific to that very release; specifically gcc 4.3.1 and 4.3.3
> seem to work fine."
>
> Since porting to a newer version is difficult for me right now, I was
> wondering if anybody worked on a patch for this specific problem.
There's no porting to be done: gcc 4.3.3 is just a bunch of bug fixes.
Andrew.
next prev parent reply other threads:[~2009-12-17 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 18:50 Jean Christophe Beyler
2009-12-16 19:37 ` Richard Guenther
2009-12-16 20:54 ` Jean Christophe Beyler
2009-12-16 21:59 ` Steven Bosscher
2009-12-17 10:27 ` Andrew Haley [this message]
2009-12-17 11:19 Jay Foad
2009-12-17 22:27 ` Jean Christophe Beyler
2009-12-18 2:29 ` Jie Zhang
2009-12-18 14:46 ` Jean Christophe Beyler
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=4B2A0791.7080509@redhat.com \
--to=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jean.christophe.beyler@gmail.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).