public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wavexx at thregr dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/69471] "-march=native" unintentionally breaks further -march/-mtune flags
Date: Tue, 01 Jun 2021 08:26:14 +0000 [thread overview]
Message-ID: <bug-69471-4-w2nBtHgjlO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-69471-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69471
--- Comment #17 from wavexx at thregr dot org ---
I wish this would be given a nudge, considering the patch. This has been pushed
to new releases since 2016 :(
It's not a show-stopper, but it does cause unexpected behavior which is quite
hard to track down and to fix as well in build systems unless you're accounting
for it from the start.
next prev parent reply other threads:[~2021-06-01 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-69471-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:59 ` jakub at gcc dot gnu.org
2021-06-01 8:07 ` rguenth at gcc dot gnu.org
2021-06-01 8:26 ` wavexx at thregr dot org [this message]
2021-06-01 11:55 ` manu at gcc dot gnu.org
2021-06-01 13:03 ` wavexx at thregr dot org
2021-06-06 13:15 ` hjl.tools at gmail dot com
2021-12-20 0:46 ` hjl.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-69471-4-w2nBtHgjlO@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: link
Be 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).