This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/69471] "-march=native" unintentionally breaks further -march/-mtune flags
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 25 Jan 2016 18:42:14 +0000
- Subject: [Bug target/69471] "-march=native" unintentionally breaks further -march/-mtune flags
- Auto-submitted: auto-generated
- References: <bug-69471-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69471
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #3 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
This is a symptom of a more general problem, which is that the general GCC
options machinery does not know which options have a single value (-march=) and
which options can have multiple values (-I). If it did, then the command-line
could be filtered before processing to keep only the last setting. Some of it
is done in prune_options but either it happens too late (after the driver has
already messed up the command-line) or it only applies to negated options.