public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/46905] New: -flto -fno-lto does not disable lto Date: Sun, 12 Dec 2010 13:50:00 -0000 [thread overview] Message-ID: <bug-46905-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46905 Summary: -flto -fno-lto does not disable lto Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: andi-gcc@firstfloor.org gcc -flto -fno-lto hello.c generates LTO objects. It should not. In large makefiles it's often convenient to use -fno... to disable something for only specific files.
next reply other threads:[~2010-12-12 13:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-12 13:50 andi-gcc at firstfloor dot org [this message] 2010-12-12 14:19 ` [Bug lto/46905] " andi-gcc at firstfloor dot org 2010-12-16 14:37 ` rguenth at gcc dot gnu.org 2010-12-19 19:36 ` ak at gcc dot gnu.org 2011-01-08 21:11 ` hubicka at gcc dot gnu.org 2011-01-08 23:35 ` andi-gcc at firstfloor dot org 2011-01-09 1:18 ` Jan Hubicka 2011-01-09 0:57 ` andi-gcc at firstfloor dot org 2011-01-09 1:28 ` hubicka at ucw dot cz 2011-10-07 5:44 ` andi-gcc at firstfloor dot org
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-46905-4@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).