public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/94842] [8/9/10 Regression] internal compiler error: in gimplify_label_expr, at gimplify.c:2573 Date: Thu, 30 Apr 2020 10:32:03 +0000 [thread overview] Message-ID: <bug-94842-4-KMJOFrEmlU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94842-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94842 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Indeed: _Atomic float x = 5; void bar (float y[(int) (x += 2)]) { } is accepted while _Atomic float x = 5; void foo (void) { void bar (float y[(int) (x += 2)]) {} } ICEs. The problem is that create_artificial_label called from build_atomic_assign from the nested function parameter declaration parsing sets LABEL_DECL to current_function_decl
next prev parent reply other threads:[~2020-04-30 10:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 6:51 [Bug c/94842] New: " anbu1024.me at gmail dot com 2020-04-29 7:18 ` [Bug c/94842] " rguenth at gcc dot gnu.org 2020-04-29 13:28 ` jakub at gcc dot gnu.org 2020-04-29 21:27 ` joseph at codesourcery dot com 2020-04-30 10:32 ` jakub at gcc dot gnu.org [this message] 2020-04-30 10:33 ` jakub at gcc dot gnu.org 2020-04-30 19:49 ` [Bug c/94842] [8/9/10/11 " cvs-commit at gcc dot gnu.org 2020-04-30 19:49 ` [Bug c/94842] [8/9/10 " jakub at gcc dot gnu.org 2020-05-07 13:27 ` cvs-commit at gcc dot gnu.org 2020-05-07 13:33 ` [Bug c/94842] [8/9 " jakub at gcc dot gnu.org 2020-05-08 3:02 ` paul.hua.gm at gmail dot com 2020-09-16 19:21 ` cvs-commit at gcc dot gnu.org 2020-09-17 17:48 ` jakub 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-94842-4-KMJOFrEmlU@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).