public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/41969] [LTO] 23% slow-down with -flto -fwhole-program Date: Fri, 06 Nov 2009 16:42:00 -0000 [thread overview] Message-ID: <20091106164215.26261.qmail@sourceware.org> (raw) In-Reply-To: <bug-41969-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rguenth at gcc dot gnu dot org 2009-11-06 16:42 ------- I'd be interested in -O3 [-fwhole-program] -fwhole-file numbers. This testcase shouldn't need any LTO to be optimized properly. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41969
next prev parent reply other threads:[~2009-11-06 16:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-06 13:27 [Bug middle-end/41969] New: " burnus at gcc dot gnu dot org 2009-11-06 16:42 ` rguenth at gcc dot gnu dot org [this message] 2009-11-06 16:46 ` [Bug middle-end/41969] " rguenth at gcc dot gnu dot org 2009-11-06 16:50 ` rguenth at gcc dot gnu dot org [not found] <bug-41969-4@http.gcc.gnu.org/bugzilla/> 2012-03-13 23:52 ` pinskia at gcc dot gnu.org 2012-03-18 16:32 ` burnus at gcc dot gnu.org 2012-04-29 18:49 ` mikolajmm at gmail dot com 2012-04-30 0:39 ` Jan Hubicka 2012-04-30 0:39 ` hubicka at ucw dot cz
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=20091106164215.26261.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).