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 target/113270] [14 Regression] AArch64 ICEs in register_tuple_type since r14-6524 Date: Mon, 08 Jan 2024 13:47:38 +0000 [thread overview] Message-ID: <bug-113270-4-WnoTXolX1N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113270-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113270 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 57005 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57005&action=edit gcc14-pr113270.patch This seems to work by making the type static to the aarch64-builtins.cc TU and using an exported function to get at the data. If anyone has ideas how to make gengtype work for this case, it might be cleaner than this...
next prev parent reply other threads:[~2024-01-08 13:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-08 11:36 [Bug target/113270] New: [14 Regression] AArch64 ICEs in register_tuple_type jakub at gcc dot gnu.org 2024-01-08 11:36 ` [Bug target/113270] " jakub at gcc dot gnu.org 2024-01-08 12:02 ` [Bug target/113270] [14 Regression] AArch64 ICEs in register_tuple_type since r14-6524 jakub at gcc dot gnu.org 2024-01-08 12:22 ` jakub at gcc dot gnu.org 2024-01-08 12:49 ` jakub at gcc dot gnu.org 2024-01-08 13:38 ` jakub at gcc dot gnu.org 2024-01-08 13:47 ` jakub at gcc dot gnu.org [this message] 2024-01-08 15:57 ` rsandifo at gcc dot gnu.org 2024-01-08 16:11 ` jakub at gcc dot gnu.org 2024-01-08 16:22 ` rsandifo at gcc dot gnu.org 2024-01-09 13:07 ` cvs-commit at gcc dot gnu.org 2024-01-09 13:38 ` 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-113270-4-WnoTXolX1N@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).