From: Ian Lance Taylor <iant@google.com>
To: Byoungyoung Lee <lifeasageek@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: How to do executable individualization using optimization options ?
Date: Sat, 07 Nov 2009 19:36:00 -0000 [thread overview]
Message-ID: <mcrtyx6t9e7.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <ba3207a80911070522q49ed7662pd3bb07b6795fe1ef@mail.gmail.com> (Byoungyoung Lee's message of "Sat\, 7 Nov 2009 22\:22\:44 +0900")
Byoungyoung Lee <lifeasageek@gmail.com> writes:
> If the optimization options provided in a different way,
> the same source codes would be compiled into different executables.
>
> In the different executables,
> the register allocation or instruction orders might be easily changed,
> but I think that's not that big change.
> What I'd like to do is to make their CFG different, while their impact
> on executing performance is reasonable.
>
> I'm reading through the compiler books and gcc internal documentations,
> but it's really hard for me to pin point what I really need to read
> and understand.
>
> So, my question is what kind of optimizing options in gcc could be
> used to do such jobs ?
> or would you recommend good references for this ?
Sorry, I don't understand the question. Are you asking what gcc
options will produce a different CFG? If so, this question would be
better asked on gcc-help@gcc.gnu.org. One answer is that you will get
a slightly different CFG from options like -funroll-loops. In general
there are a number of options which could change the CFG. But I'm not
sure why you are asking the question.
Ian
next prev parent reply other threads:[~2009-11-07 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 13:22 Byoungyoung Lee
2009-11-07 19:36 ` Ian Lance Taylor [this message]
2009-11-09 3:01 ` Byoungyoung Lee
-- strict thread matches above, loose matches on Subject: below --
2009-11-07 9:38 Byoungyoung Lee
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=mcrtyx6t9e7.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=lifeasageek@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).