public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/49700] LTO compile time hog Date: Tue, 08 May 2012 18:59:00 -0000 [thread overview] Message-ID: <bug-49700-4-mShvUGrqwB@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 Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |FIXED --- Comment #9 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2012-05-08 18:52:12 UTC --- trying 4.7.X instead it actually looks very reasonable now. Using -flto=jobserver -fuse-linker-plugin -ftime-report -O3 -march=native -ffast-math -g -ffree-form I get CP2K to build in 4min on a 32 cores server. The time report also looks OK. I'll close this PR as fixed (to issue with 4.8 is tracked in PR 45586).
prev parent reply other threads:[~2012-05-08 18:53 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 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 [this message]
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-mShvUGrqwB@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: 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).