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++/97990] [11/12/13 Regression] ICE: ‘verify_type’ failed with vector types and non-PODs since r6-5222-gba6a6a1d44c17f25
Date: Fri, 16 Feb 2024 18:51:04 +0000 [thread overview]
Message-ID: <bug-97990-4-oxE3fSKnhS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97990-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97990
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[11/12/13/14 Regression] |[11/12/13 Regression] ICE:
|ICE: ‘verify_type’ failed |‘verify_type’ failed with
|with vector types and |vector types and non-PODs
|non-PODs since |since
|r6-5222-gba6a6a1d44c17f25 |r6-5222-gba6a6a1d44c17f25
Known to work| |14.0
--- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #11)
> Looks like r14-5934-gf26d68d5d128c8:
>
> commit f26d68d5d128c86faaceeb81b1e8f22254ad53df
> Author: Richard Biener <rguenther@suse.de>
> Date: Tue Nov 28 12:36:21 2023 +0100
>
> middle-end/112732 - stray TYPE_ALIAS_SET in type variant
>
> fixed this.
Yes that looks like the correct fix even and PR 112732 does look like the same
issue here except a different path to create the type variant.
next prev parent reply other threads:[~2024-02-16 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 16:31 [Bug tree-optimization/97990] New: ICE: ‘verify_type’ failed doko at debian dot org
2020-11-26 9:57 ` [Bug tree-optimization/97990] [8/9/10/11 Regression] ICE: ‘verify_type’ failed since r6-5222-gba6a6a1d44c17f25 marxin at gcc dot gnu.org
2021-05-14 9:54 ` [Bug tree-optimization/97990] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:19 ` rguenth at gcc dot gnu.org
2022-05-27 9:43 ` [Bug tree-optimization/97990] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-07-07 9:09 ` [Bug tree-optimization/97990] [10/11/12/13/14 " pinskia at gcc dot gnu.org
2023-07-07 9:17 ` [Bug c++/97990] [10/11/12/13/14 Regression] ICE: ‘verify_type’ failed with vector types and non-PODs " pinskia at gcc dot gnu.org
2023-07-07 9:19 ` pinskia at gcc dot gnu.org
2023-07-07 10:38 ` [Bug c++/97990] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-08 1:26 ` pinskia at gcc dot gnu.org
2024-02-16 18:44 ` mpolacek at gcc dot gnu.org
2024-02-16 18:51 ` pinskia at gcc dot gnu.org [this message]
2024-02-16 19:01 ` [Bug c++/97990] [11/12/13 " cvs-commit at gcc dot gnu.org
2024-05-08 12:45 ` cvs-commit at gcc dot gnu.org
2024-05-08 12:46 ` [Bug c++/97990] [11/12 " rguenth at gcc dot gnu.org
2024-06-04 8:08 ` 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-97990-4-oxE3fSKnhS@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).