From: Richard Biener <richard.guenther@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
Gerald Pfeifer <gerald@pfeifer.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] doc: discourage use of __attribute__((optimize())) in production code
Date: Mon, 14 Dec 2015 09:01:00 -0000 [thread overview]
Message-ID: <CAFiYyc25Q7kMkjvbTfgBqUELyw4mop6ysT7aAJAz2NruV7sa2w@mail.gmail.com> (raw)
In-Reply-To: <87mvtet8t6.fsf@tassilo.jf.intel.com>
On Sun, Dec 13, 2015 at 9:03 PM, Andi Kleen <andi@firstfloor.org> wrote:
> Markus Trippelsdorf <markus@trippelsdorf.de> writes:
>
>> Many developers are still using __attribute__((optimize())) in
>> production code, although it quite broken.
>
> Wo reads documentation? @) If you want to discourage it better warn once
> at runtime.
We're also quite heavily using it in LTO internally now.
Richard.
> -Andi
next prev parent reply other threads:[~2015-12-14 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 8:19 Markus Trippelsdorf
2015-12-13 20:03 ` Andi Kleen
2015-12-14 9:01 ` Richard Biener [this message]
2015-12-14 16:21 ` Trevor Saunders
2015-12-14 16:41 ` Markus Trippelsdorf
2015-12-14 17:04 ` Manuel López-Ibáñez
2015-12-14 18:57 ` Trevor Saunders
2016-04-28 15:32 ` Jeff Law
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=CAFiYyc25Q7kMkjvbTfgBqUELyw4mop6ysT7aAJAz2NruV7sa2w@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=markus@trippelsdorf.de \
/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).