public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/97206] [11 Regression] internal compiler error: in composite_type, at c/c-typeck.c:447 since r11-3303-g6450f07388f9fe57 Date: Tue, 29 Sep 2020 17:03:08 +0000 [thread overview] Message-ID: <bug-97206-4-KsRxgrL5hK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97206-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97206 --- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> --- Testing this fix: diff --git a/gcc/attribs.c b/gcc/attribs.c index abc75368e6c..262e4b8f7b9 100644 --- a/gcc/attribs.c +++ b/gcc/attribs.c @@ -2278,7 +2278,7 @@ attr_access::array_as_string (tree type) const else if (minsize) index_type = build_index_type (size_int (minsize - 1)); - artype = build_array_type (eltype, index_type); + artype = build_nonshared_array_type (eltype, index_type); if (static_p || vla_p) {
next prev parent reply other threads:[~2020-09-29 17:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-25 9:45 [Bug c/97206] New: [11-regression] internal compiler error: in composite_type, at c/c-typeck.c:447 slyfox at gcc dot gnu.org 2020-09-25 9:57 ` [Bug c/97206] " slyfox at gcc dot gnu.org 2020-09-25 10:14 ` [Bug c/97206] [11 Regression] internal compiler error: in composite_type, at c/c-typeck.c:447 since r11-3303-g6450f07388f9fe57 marxin at gcc dot gnu.org 2020-09-25 10:22 ` rguenth at gcc dot gnu.org 2020-09-25 17:40 ` msebor at gcc dot gnu.org 2020-09-26 0:03 ` msebor at gcc dot gnu.org 2020-09-29 1:46 ` msebor at gcc dot gnu.org 2020-09-29 17:03 ` msebor at gcc dot gnu.org [this message] 2020-09-29 21:41 ` msebor at gcc dot gnu.org 2020-09-30 19:04 ` cvs-commit at gcc dot gnu.org 2020-09-30 19:05 ` msebor 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-97206-4-KsRxgrL5hK@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).