public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at pci dot uzh.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/49700] LTO compile time hog
Date: Tue, 12 Jul 2011 10:18:00 -0000 [thread overview]
Message-ID: <bug-49700-4-c7eK00ECTn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49700-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49700
--- Comment #5 from Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> 2011-07-12 10:17:54 UTC ---
(In reply to comment #3)
> Oh, so it's a sum ...
>
> Well, the I suppose you run into the usual array-prefetching compile-time hog.
> Try -fno-prefetch-loop-arrays.
This seems to reduce the time by 5x. On a non-LTO run, this doesn't matter, but
I assume LTO makes more info available that triggers some action by that pass.
next prev parent reply other threads:[~2011-07-12 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 6:29 [Bug lto/49700] New: " Joost.VandeVondele at pci dot uzh.ch
2011-07-11 9:21 ` [Bug lto/49700] " rguenth at gcc dot gnu.org
2011-07-11 9:29 ` jakub at gcc dot gnu.org
2011-07-11 9:33 ` rguenth at gcc dot gnu.org
2011-07-11 19:57 ` pinskia at gcc dot gnu.org
2011-07-12 10:18 ` Joost.VandeVondele at pci dot uzh.ch [this message]
2011-07-12 14:41 ` Joost.VandeVondele at pci dot uzh.ch
2012-05-07 12:41 ` rguenth at gcc dot gnu.org
2012-05-07 19:18 ` Joost.VandeVondele at mat dot ethz.ch
2012-05-08 18:59 ` Joost.VandeVondele at mat dot ethz.ch
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=bug-49700-4-c7eK00ECTn@http.gcc.gnu.org/bugzilla/ \
--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: 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).