From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Question on Taming the Optimizer
Date: Wed, 28 Sep 2011 15:00:00 -0000 [thread overview]
Message-ID: <4E82E1E6.1070604@redhat.com> (raw)
In-Reply-To: <CAH8yC8kV6L_GOQNY9Ypo-63XC_cM4gPhAt_nA_L6aiYXm1x=_w@mail.gmail.com>
On 09/28/2011 12:41 AM, Jeffrey Walton wrote:
>
> What is the preferred way to tame the optimizer when two class
> functions are producing incorrect results?
I wouldn't. I'd try to isolate the problem into a test case that
demonstrates the problem.
Andrew.
prev parent reply other threads:[~2011-09-28 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 5:01 Jeffrey Walton
2011-09-28 6:15 ` Jonathan Wakely
2011-09-28 7:37 ` Jeffrey Walton
2011-09-28 14:36 ` Jonathan Wakely
2011-09-28 15:00 ` Andrew Haley [this message]
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=4E82E1E6.1070604@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@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).