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 lto/42581] "gcc -v" doesn't work with lto Date: Sat, 02 Jan 2010 20:26:00 -0000 [thread overview] Message-ID: <20100102202626.29716.qmail@sourceware.org> (raw) In-Reply-To: <bug-42581-682@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rguenth at gcc dot gnu dot org 2010-01-02 20:26 ------- Confirmed. But -save-temps also doesn't work completely for -fwhopr (and you need to set the collect2 env vars for -fwhopr). The proper fix for 4.6 is to move most of the LTO handling to the gcc driver, away from collect2, lto-wrapper and lto1. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-01-02 20:26:26 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42581
next prev parent reply other threads:[~2010-01-02 20:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-02 19:14 [Bug lto/42581] New: " hjl dot tools at gmail dot com 2010-01-02 20:26 ` rguenth at gcc dot gnu dot org [this message] 2010-01-03 19:16 ` [Bug lto/42581] " hjl dot tools at gmail dot com 2010-01-04 14:43 ` hjl at gcc dot gnu dot org 2010-01-04 17:34 ` hjl dot tools at gmail dot com
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=20100102202626.29716.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).