public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106173] -fleading-underscore option inactive although reported as active
Date: Sun, 03 Jul 2022 22:49:16 +0000 [thread overview]
Message-ID: <bug-106173-4-ZtQdexVPfv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106173-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106173
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |12.1.0
Known to fail| |11.1.0
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note in GCC 11+, you need to add --help to get which option has enabled or not.
Also note in GCC 12+ we get:
-fleading-underscore
Which means it is not enabled or disabled. Still trying to figure out what
changed that.
next prev parent reply other threads:[~2022-07-03 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 12:37 [Bug c/106173] New: " mcn at onet dot pl
2022-07-03 22:49 ` pinskia at gcc dot gnu.org [this message]
2022-07-08 12:51 ` [Bug middle-end/106173] " marxin at gcc dot gnu.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-106173-4-ZtQdexVPfv@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).