public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/112732] during IPA pass: *free_lang_data ICE: 'verify_type' failed: type variant with 'TYPE_ALIAS_SET_KNOWN_P' with -Os -Wstrict-aliasing=2 -flto Date: Tue, 28 Nov 2023 11:35:14 +0000 [thread overview] Message-ID: <bug-112732-4-Hw52ZAkmKb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112732-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112732 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Keywords| |ice-checking CC| |hubicka at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- The vector type is built as a distinct type copy from a vector type that has the alias set already set (by the diagnostic code). #0 0x0000000001adac14 in build_opaque_vector_type ( innertype=<integer_type 0x7ffff6a2b9d8 __int128>, nunits=...) at /home/rguenther/src/trunk/gcc/tree.cc:10271 #1 0x0000000000d97c7c in build_binary_op (location=279873, code=EQ_EXPR, orig_op0=<var_decl 0x7ffff6a19cf0 w>, orig_op1=<var_decl 0x7ffff6a19d80 d>, convert_p=true) at /home/rguenther/src/trunk/gcc/c/c-typeck.cc:12617 #2 0x0000000000d7230f in parser_build_binary_op (location=279873, code=EQ_EXPR, arg1=..., arg2=...) at /home/rguenther/src/trunk/gcc/c/c-typeck.cc:3766 I think given this checking that build_opaque_vector_type should clear TYPE_ALIAS_SET.
next prev parent reply other threads:[~2023-11-28 11:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-27 19:05 [Bug lto/112732] New: " zsojka at seznam dot cz 2023-11-28 11:25 ` [Bug lto/112732] " rguenth at gcc dot gnu.org 2023-11-28 11:35 ` rguenth at gcc dot gnu.org [this message] 2023-11-28 15:58 ` cvs-commit at gcc dot gnu.org 2023-11-28 15:59 ` rguenth at gcc dot gnu.org 2024-05-08 12:45 ` cvs-commit at gcc dot gnu.org 2024-06-04 8:08 ` cvs-commit at gcc dot gnu.org 2024-07-08 13:05 ` 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-112732-4-Hw52ZAkmKb@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).