public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97186] [11 Regression] ICE: Segmentation fault (in maybe_instantiate_noexcept) Date: Thu, 24 Sep 2020 12:32:18 +0000 [thread overview] Message-ID: <bug-97186-4-uFEXU0Uam6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97186-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97186 --- Comment #2 from Nathan Sidwell <nathan at gcc dot gnu.org> --- The error abount conversion failure, if it is a bug, is unrelated to the ICE. I say 'if', because I think there have been changes in regards to whether functions decay to pointers which can be implicitly converted to bool in constant exprs. Not digging into that right now though.
next prev parent reply other threads:[~2020-09-24 12:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-24 4:14 [Bug c++/97186] New: " asolokha at gmx dot com 2020-09-24 7:17 ` [Bug c++/97186] " rguenth at gcc dot gnu.org 2020-09-24 7:53 ` marxin at gcc dot gnu.org 2020-09-24 11:48 ` nathan at gcc dot gnu.org 2020-09-24 12:32 ` nathan at gcc dot gnu.org [this message] 2020-09-24 13:23 ` cvs-commit at gcc dot gnu.org 2020-09-24 13:24 ` nathan 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-97186-4-uFEXU0Uam6@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).