public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111224] modules: xtreme-header-1_a.H etc. ICE (in core_vals, at cp/module.cc:6108) on AArch64 with SVE types
Date: Mon, 04 Mar 2024 01:29:55 +0000 [thread overview]
Message-ID: <bug-111224-4-E5zm0fqjrO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111224-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111224
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Nathaniel Shead from comment #7)
> Created attachment 57586 [details]
> Untested patch to implement POLY_INT_CST in modules
>
> Here's a potential fix for this issue. But I only have access to an x86_64
> machine currently, so this is completely untested.
I can test it but it won't be until the middle of this up comming week.
next prev parent reply other threads:[~2024-03-04 1:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 11:42 [Bug c++/111224] New: modules: xtreme-header-1_a.H etc. ICE (in core_vals, at cp/module.cc:6108) on AArch64 xry111 at gcc dot gnu.org
2023-08-29 11:44 ` [Bug c++/111224] " xry111 at gcc dot gnu.org
2023-08-29 11:57 ` xry111 at gcc dot gnu.org
2023-08-29 12:34 ` xry111 at gcc dot gnu.org
2023-08-29 12:36 ` xry111 at gcc dot gnu.org
2024-02-11 18:36 ` [Bug c++/111224] modules: xtreme-header-1_a.H etc. ICE (in core_vals, at cp/module.cc:6108) on AArch64 with SVE types pinskia at gcc dot gnu.org
2024-02-11 18:38 ` pinskia at gcc dot gnu.org
2024-03-01 12:52 ` nshead at gcc dot gnu.org
2024-03-01 17:39 ` ppalka at gcc dot gnu.org
2024-03-04 1:29 ` pinskia at gcc dot gnu.org [this message]
2024-03-09 2:43 ` nshead at gcc dot gnu.org
2024-03-12 13:42 ` cvs-commit 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-111224-4-E5zm0fqjrO@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).