public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Byoungyoung Lee <override@postech.ac.kr>
To: gcc@gcc.gnu.org
Subject: How to do executable individualization using optimization options ?
Date: Sat, 07 Nov 2009 09:38:00 -0000	[thread overview]
Message-ID: <ba3207a80911070138t45ea45ch57a0cbf39f5cc543@mail.gmail.com> (raw)

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 ?

Regards,
Byoungyoung Lee

             reply	other threads:[~2009-11-07  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07  9:38 Byoungyoung Lee [this message]
2009-11-07 13:22 Byoungyoung Lee
2009-11-07 19:36 ` Ian Lance Taylor
2009-11-09  3:01   ` 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=ba3207a80911070138t45ea45ch57a0cbf39f5cc543@mail.gmail.com \
    --to=override@postech.ac.kr \
    --cc=gcc@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).