public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d dot g dot gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/42520] New: lto1 does not see -march and -mtune options Date: Mon, 28 Dec 2009 19:30:00 -0000 [thread overview] Message-ID: <bug-42520-16926@http.gcc.gnu.org/bugzilla/> (raw) For example, `gcc -march=pentium -flto -fuse-linker-plugin main.c' causes this: /usr/local/libexec/gcc/i686-pc-linux-gnu/4.5.0/lto1 -quiet -dumpbase cc0AFVJ9 -mtune=generic -march=pentium4 -auxbase-strip /tmp/cc7X43Dc.lto.o -fuse-linker-plugin -fresolution @/tmp/ccoGGiIc -o /tmp/ccCcL0Ff.s "-mtune=generic -march=pentium4" appears because GCC (4.5.0 20091224) was configured with "--with-arch=pentium4 --with-tune=generic" options. -- Summary: lto1 does not see -march and -mtune options Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: d dot g dot gorbachev at gmail dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42520
next reply other threads:[~2009-12-28 19:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-28 19:30 d dot g dot gorbachev at gmail dot com [this message] 2009-12-31 15:14 ` [Bug driver/42520] " rguenth at gcc dot gnu dot org 2010-01-01 16:51 ` d dot g dot gorbachev at gmail dot com 2010-01-01 17:16 ` rguenth at gcc dot gnu dot org 2010-01-01 17:53 ` d dot g dot gorbachev at gmail dot com 2010-01-01 20:26 ` steven at gcc dot gnu dot org 2010-01-03 22:29 ` [Bug driver/42520] lto1 does not see -march and -mtune options with -fuse-linker-plugin rguenth at gcc dot gnu dot org 2010-01-04 0:53 ` hjl at gcc dot gnu dot org 2010-01-04 4:28 ` 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=bug-42520-16926@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).