From: Adrian Bentley <adruab@voria.com>
To: Eljay Love-Jensen <eljay@adobe.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Weird optimization bug...?
Date: Thu, 03 Jun 2004 21:17:00 -0000 [thread overview]
Message-ID: <1086297425.18157.38.camel@localhost> (raw)
In-Reply-To: <6.0.3.0.2.20040603132957.02031898@iplan-mn.corp.adobe.com>
So I looked at the assembly and didn't find anything super glaring. The
compiled code was very different, so I'm not surprised the result is
different. I haven't gotten any closer to figuring out what kind of
mis-optimization it's doing (or if it's something else totally
bizarre). Any other pointers for narrowing it down, or should I just
hack it and wait for a new version of gcc to come out :).
Thanks again,
Adruab
On Thu, 2004-06-03 at 11:36, Eljay Love-Jensen wrote:
> Hi Adruab.
>
> >However, if that was the case, inserting a random function into the code
> certain shouldn't fix the problem :P.
>
> Inserting a random function into the code can affect the optimizer, which
> can mask the problem.
>
> I recommend taking a look at the assembly file to see what's different
> between having and not having the extra function present, in the optimized
> code.
>
> You can use the "-save-temps" to keep the assembly file around, and
> "-fverbose-asm" for extra blather.
>
> HTH,
> --Eljay
>
>
>
next prev parent reply other threads:[~2004-06-03 21:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 20:24 Adrian Bentley
2004-06-03 11:26 ` Eljay Love-Jensen
2004-06-03 17:24 ` Adrian Bentley
2004-06-03 18:37 ` Eljay Love-Jensen
2004-06-03 19:11 ` Adrian Bentley
2004-06-03 21:17 ` Adrian Bentley [this message]
2004-06-03 23:06 ` Adrian Bentley
2004-06-04 3:00 ` Ian Lance Taylor
2004-06-05 19:09 ` Adrian Bentley
2004-06-05 23:31 ` Ian Lance Taylor
2004-06-06 0:47 ` Ken Foskey
2004-06-05 20:21 ` Adrian Bentley
[not found] ` <m3aczh4m55.fsf@gossamer.airs.com>
2004-06-06 16:44 ` Adrian Bentley
2004-06-06 22:23 ` Ian Lance Taylor
2004-06-03 19:13 lrtaylor
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=1086297425.18157.38.camel@localhost \
--to=adruab@voria.com \
--cc=eljay@adobe.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).