From: kevin diggs <diggskevin38@gmail.com>
To: Andi Hellmund <mail@andihellmund.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: options for later passes
Date: Tue, 22 Feb 2011 00:34:00 -0000 [thread overview]
Message-ID: <AANLkTim-hv364HV_ZubxXZwYkVykVaf0kvicdh+s3==y@mail.gmail.com> (raw)
In-Reply-To: <4D62F0C9.1010305@andihellmund.com>
On Mon, Feb 21, 2011 at 5:10 PM, Andi Hellmund <mail@andihellmund.com> wrote:
>
>> Does anyone else need the -O2?
>
> No, only the compiler (cc1, cc1plus, ...)
>
Can I assume this also includes all of -O's -f friends?
Thanks!
kevin
next prev parent reply other threads:[~2011-02-22 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 20:58 kevin diggs
2011-02-21 23:37 ` Andi Hellmund
2011-02-22 0:34 ` kevin diggs [this message]
2011-02-22 15:47 ` Andi Hellmund
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='AANLkTim-hv364HV_ZubxXZwYkVykVaf0kvicdh+s3==y@mail.gmail.com' \
--to=diggskevin38@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mail@andihellmund.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).