From: slnc <s@slnc.me>
To: "John (Eljay) Love-Jensen" <eljay@adobe.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Optimization flags not working (GCC 4.2.4)
Date: Fri, 03 Apr 2009 23:55:00 -0000 [thread overview]
Message-ID: <49D6A1EC.4060505@slnc.me> (raw)
In-Reply-To: <204DEA5423F3BF47A6EE88C4E2979EC66BE84EDAE6@nambx04.corp.adobe.com>
Hi John,
Thank you but -O0 makes no difference.
gcc -c -g -O0 -fdefer-pop -fdelayed-branch -fguess-branch-probability
-fcprop-registers -fif-conversion -fif-conversion2 -ftree-ccp -ftree-dce
-ftree-dominator-opts -ftree-dse -ftree-ter -ftree-lrs -ftree-sra
-ftree-copyrename -ftree-fre -ftree-ch -funit-at-a-time
-fmerge-constants main.c
(those are all gcc 4.2.4 optimization flags for level -O1 according to
the docs) generates the same unoptimized code. Changing -O0 with -O1
generates the optimized version.
John (Eljay) Love-Jensen wrote:
> Hi Juan,
>
> If you are not optimizing (-O0), the optimization -f flags have no effect.
>
> HTH,
> --Eljay
>
--
Juan Alonso
next prev parent reply other threads:[~2009-04-03 23:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 19:31 slnc
2009-04-03 21:45 ` John (Eljay) Love-Jensen
2009-04-03 23:55 ` slnc [this message]
2009-04-04 0:31 ` David Daney
2009-04-04 0:47 ` slnc
2009-04-04 0:58 ` Robert William Fuller
2009-04-04 1:01 ` Ian Lance Taylor
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=49D6A1EC.4060505@slnc.me \
--to=s@slnc.me \
--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).