public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "familiebaumanns at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96141] ICE in gimplify: Coroutine and noexcept(false) destructor cause: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:2817 Date: Sun, 12 Jul 2020 09:30:29 +0000 [thread overview] Message-ID: <bug-96141-4-aoGXv8SQqy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96141-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96141 --- Comment #3 from Bernd Baumanns <familiebaumanns at gmail dot com> --- Is there something missing in that if? What must be changed? This is assert fails: /* ??? If this is a local variable, and it has not been seen in any outer BIND_EXPR, then it's probably the result of a duplicate declaration, for which we've already issued an error. It would be really nice if the front end wouldn't leak these at all. Currently the only known culprit is C++ destructors, as seen in g++.old-deja/g++.jason/binding.C. */ if (VAR_P (decl) && !DECL_SEEN_IN_BIND_EXPR_P (decl) && !TREE_STATIC (decl) && !DECL_EXTERNAL (decl) && decl_function_context (decl) == current_function_decl) { gcc_assert (seen_error ()); return GS_ERROR; }
next prev parent reply other threads:[~2020-07-12 9:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-09 21:20 [Bug c++/96141] New: " familiebaumanns at gmail dot com 2020-07-09 21:26 ` [Bug c++/96141] " familiebaumanns at gmail dot com 2020-07-09 21:28 ` familiebaumanns at gmail dot com 2020-07-12 9:30 ` familiebaumanns at gmail dot com [this message] 2021-07-18 23:48 ` [Bug c++/96141] ICE in gimplify: " pinskia 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-96141-4-aoGXv8SQqy@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).