public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105492] [13 Regression] ICE in set_underlying_type, at c-family/c-common.cc:8164 since r13-57-g0aa277bf0b4b7943 Date: Mon, 16 May 2022 21:34:07 +0000 [thread overview] Message-ID: <bug-105492-4-xkztHky4xJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105492-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105492 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:ed12749a3c9d9569a2c23df2e0db2136dcd3512d commit r13-515-ged12749a3c9d9569a2c23df2e0db2136dcd3512d Author: Jason Merrill <jason@redhat.com> Date: Thu May 5 11:03:44 2022 -0400 attribs: fix typedefs in generic code [PR105492] In my patch for PR100545 I added an assert to check for broken typedefs in set_underlying_type, and it found one in this case: rs6000_handle_altivec_attribute had the same problem as handle_mode_attribute. So let's move the fixup into decl_attributes. PR c/105492 gcc/ChangeLog: * attribs.cc (decl_attributes): Fix broken typedefs here. gcc/c-family/ChangeLog: * c-attribs.cc (handle_mode_attribute): Don't fix broken typedefs here.
next prev parent reply other threads:[~2022-05-16 21:34 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-05 11:40 [Bug c/105492] New: [13 Regression] ICE in set_underlying_type, at c-family/c-common.cc:8164 asolokha at gmx dot com 2022-05-05 12:16 ` [Bug c/105492] " rguenth at gcc dot gnu.org 2022-05-05 13:59 ` [Bug c/105492] [13 Regression] ICE in set_underlying_type, at c-family/c-common.cc:8164 since r13-57-g0aa277bf0b4b7943 marxin at gcc dot gnu.org 2022-05-05 14:24 ` jason at gcc dot gnu.org 2022-05-15 8:30 ` slyfox at gcc dot gnu.org 2022-05-15 16:26 ` jason at gcc dot gnu.org 2022-05-16 21:34 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-16 21:40 ` jason 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-105492-4-xkztHky4xJ@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).