From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Pengfei Yuan <0xcoolypf@gmail.com>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Why not build kernel with -O3
Date: Wed, 08 Apr 2015 09:53:35 -0400 [thread overview]
Message-ID: <552532DF.7060004@gmail.com> (raw)
In-Reply-To: <CACmZjJJd0t_fSQMATN=-LJwm683+tqR90sPPAaCUCvNJ+P8MoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On 2015-04-08 09:19, Pengfei Yuan wrote:
> 2015-04-08 20:06 GMT+08:00 Austin S Hemmelgarn <ahferroin7@gmail.com>:
>> I can't remember any off the top of my head, but it does say explicitly in
>> the GCC manual to be careful with -O3. IIRC, most of the issues relate to
>> -O3 enabling -ffast-math (which tends to really mess with code that expects
>> strict IEEE 754 compliance), so it may not be as much of an issue for kernel
>> code. You might look into some of the projects that use -O3 by default (I
>> think most of the Mozilla so0ftware does these days, and I know that there
>> are others, I just can't remember what right now).
>>
>
> I am afraid you are talking about -Ofast, not -O3.
> See https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
>
> Yuan
>
You're right, I had been looking at the wrong paragraph in the info
manual. Sorry about any confusion.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2015-04-08 13:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 3:37 Why not build kernel with -O3 Pengfei Yuan
2015-04-07 6:43 ` Mike Galbraith
2015-04-07 7:07 ` Boaz Harrosh
2015-04-07 8:29 ` Mike Galbraith
2015-04-07 7:56 ` Pengfei Yuan
2015-04-07 10:09 ` Mike Galbraith
2015-04-07 18:05 ` Austin S Hemmelgarn
2015-04-08 1:00 ` Pengfei Yuan
2015-04-08 12:06 ` Austin S Hemmelgarn
2015-04-08 12:57 ` One Thousand Gnomes
2015-04-08 13:19 ` Pengfei Yuan
2015-04-08 13:53 ` Austin S Hemmelgarn [this message]
2015-04-08 12:19 ` Richard Weinberger
2015-04-08 12:49 ` Austin S Hemmelgarn
2015-04-08 13:16 ` Pengfei Yuan
2015-04-08 13:21 ` Richard Weinberger
2015-04-27 20:37 ` Pavel Machek
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=552532DF.7060004@gmail.com \
--to=ahferroin7@gmail.com \
--cc=0xcoolypf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=umgwanakikbuti@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 NNTP newsgroup(s).