public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/34852] [4.3 Regression] Revision 131576 miscompiled 178.galgel
Date: Sun, 20 Jan 2008 15:53:00 -0000 [thread overview]
Message-ID: <20080120153421.3863.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34852-682@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from ubizjak at gmail dot com 2008-01-20 15:34 -------
(In reply to comment #3)
> Double checking patch, I don't see obvious mistakes. Since the patch should
> only affect register allocation decisions, either we see a latent bug, or
> another example of x86 extra precision causing FP program to misbehave. I used
> to have LD_PRELOAD library to set 64bit precision that often helped, I will
You can add -mpc=64 to your compile flags instead of LD_PRELOAD trick.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34852
next prev parent reply other threads:[~2008-01-20 15:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 15:35 [Bug middle-end/34852] New: " hjl dot tools at gmail dot com
2008-01-18 16:11 ` [Bug middle-end/34852] " rguenth at gcc dot gnu dot org
2008-01-18 20:45 ` pinskia at gcc dot gnu dot org
2008-01-20 12:25 ` hubicka at gcc dot gnu dot org
2008-01-20 15:53 ` ubizjak at gmail dot com [this message]
2008-01-20 16:59 ` hjl dot tools at gmail dot com
2008-01-20 16:59 ` hjl dot tools at gmail dot com
2008-01-20 17:00 ` hjl dot tools at gmail dot com
2008-01-21 4:26 ` hjl dot tools at gmail dot com
2008-01-21 10:05 ` hubicka at ucw dot cz
2008-01-21 10:08 ` hubicka at ucw dot cz
2008-01-21 10:11 ` hubicka at ucw dot cz
2008-01-21 10:16 ` hubicka at ucw dot cz
2008-01-21 15:36 ` hjl dot tools at gmail dot com
2008-01-21 16:14 ` hjl dot tools at gmail dot com
2008-01-21 16:58 ` hubicka at ucw dot cz
2008-01-21 21:00 ` hjl dot tools at gmail dot com
2008-01-22 20:22 ` rguenth at gcc dot gnu dot org
2008-01-22 20:30 ` hubicka at ucw dot cz
2008-01-23 22:33 ` rguenth 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=20080120153421.3863.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).