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 12:22:44 +0000	[thread overview]
Message-ID: <bug-113270-4-8GMiain7F0@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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ktkachov at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't really know why, not sure if GTY types simply must not appear in target
headers other than the main one or one needs to mark such headers somehow such
that gengtype is aware of those, but the generated gt-aarch64-builtins.h after
the change loses:
@@ -58,34 +58,6 @@ EXPORTED_CONST struct ggc_root_tab gt_gg
     &gt_pch_nx_tree_node
   },
   {
-    &aarch64_simd_types[0].name,
-    1 * ARRAY_SIZE (aarch64_simd_types),
-    sizeof (aarch64_simd_types[0]),
-    (gt_pointer_walker) &gt_ggc_m_S,
-    (gt_pointer_walker) &gt_pch_n_S
-  },
-  {
-    &aarch64_simd_types[0].mangle,
-    1 * ARRAY_SIZE (aarch64_simd_types),
-    sizeof (aarch64_simd_types[0]),
-    (gt_pointer_walker) &gt_ggc_m_S,
-    (gt_pointer_walker) &gt_pch_n_S
-  },
-  {
-    &aarch64_simd_types[0].itype,
-    1 * ARRAY_SIZE (aarch64_simd_types),
-    sizeof (aarch64_simd_types[0]),
-    &gt_ggc_mx_tree_node,
-    &gt_pch_nx_tree_node
-  },
-  {
-    &aarch64_simd_types[0].eltype,
-    1 * ARRAY_SIZE (aarch64_simd_types),
-    sizeof (aarch64_simd_types[0]),
-    &gt_ggc_mx_tree_node,
-    &gt_pch_nx_tree_node
-  },
-  {
     &aarch64_builtin_decls[0],
     1 * (AARCH64_BUILTIN_MAX),
     sizeof (aarch64_builtin_decls[0]),
@@ -95,8 +67,3 @@ EXPORTED_CONST struct ggc_root_tab gt_gg
   LAST_GGC_ROOT_TAB
 };

-EXPORTED_CONST struct ggc_root_tab gt_pch_rs_gt_aarch64_builtins_h[] = {
-  { &aarch64_simd_types, 1, sizeof (aarch64_simd_types), NULL, NULL },
-  LAST_GGC_ROOT_TAB
-};
-
where the former is I believe what breaks the PCH.

  parent reply	other threads:[~2024-01-08 12:22 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 [this message]
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
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-8GMiain7F0@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: link
Be 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).