public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103686] ICE in rs6000_expand_new_builtin at rs6000-call.c:15946
Date: Tue, 04 Jan 2022 15:18:44 +0000 [thread overview]
Message-ID: <bug-103686-4-lZu7lI2gI2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103686-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103686
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |willschm at gcc dot gnu.org
--- Comment #9 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #8)
> It is an internal (debugging) option. It isn't documented in the manual, but
> indeed it is not marked as Undocumented in rs6000.opt .
Will added this and the last time we talked, he said he added it mainly for
debugging purposes when he was adding some rs6000 specific gimple builtin
expansion code. To his knowledge, we don't need/want this anymore, so I
believe the correct fix here is to just remove the option now (assuming it
really is undocumented).
next prev parent reply other threads:[~2022-01-04 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 13:54 [Bug target/103686] New: " marxin at gcc dot gnu.org
2021-12-13 13:54 ` [Bug target/103686] " marxin at gcc dot gnu.org
2021-12-13 14:54 ` wschmidt at gcc dot gnu.org
2021-12-14 15:49 ` bergner at gcc dot gnu.org
2021-12-14 16:02 ` bergner at gcc dot gnu.org
2021-12-14 16:52 ` wschmidt at gcc dot gnu.org
2021-12-14 16:53 ` wschmidt at gcc dot gnu.org
2021-12-14 17:00 ` wschmidt at gcc dot gnu.org
2022-01-04 10:00 ` rguenth at gcc dot gnu.org
2022-01-04 10:15 ` segher at gcc dot gnu.org
2022-01-04 15:18 ` bergner at gcc dot gnu.org [this message]
2022-01-19 22:19 ` wschmidt at gcc dot gnu.org
2022-01-20 16:19 ` willschm at gcc dot gnu.org
2022-02-03 17:17 ` cvs-commit at gcc dot gnu.org
2022-02-03 17:24 ` wschmidt 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-103686-4-lZu7lI2gI2@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).