From: jgrant@reflectionsinteractive.com
To: ian@wasabisystems.com
Cc: gcc@gcc.gnu.org
Subject: RE: Optimisation options turned on at a certain level
Date: Mon, 22 Dec 2003 11:00:00 -0000 [thread overview]
Message-ID: <A91F89184D69D411A4E40008C784F4970243FB09@MR-T> (raw)
Hello Ian,
Thank you for the link. Very useful.
I was hoping for a list of the options as well as the text describing the
different levels.
Could this be added the documentation? so its clear exactly what is being
done by which options are being passed. Perhaps something like:
Optimisation level -O1
-fomit-frame-pointer When possible do not
generate stack frames
-fdefer-pop Defer popping functions args
from stack until later
-fthread-jumps Perform jump threading
optimisations
-fdelayed-branch Attempt to fill delay slots
of branch instructions
Optimisation level -O3
-funroll-loops
etc
(I these may not be accurate, just for illustration)
What do you think?
Kind regards
Jonathan
next reply other threads:[~2003-12-22 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 11:00 jgrant [this message]
2003-12-22 19:31 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 19:31 jgrant
2004-01-18 18:26 jgrant
2004-01-18 19:08 ` Ian Lance Taylor
2004-01-18 19:29 ` Andrew Pinski
2003-12-21 18:30 jgrant
2003-12-21 18:36 ` 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=A91F89184D69D411A4E40008C784F4970243FB09@MR-T \
--to=jgrant@reflectionsinteractive.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.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).