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 tree-optimization/113736] ICE: verify_gimple failed: incompatible types in 'PHI' argument 0 with _BitInt() struct copy to __seg_fs/gs Date: Sat, 03 Feb 2024 10:25:17 +0000 [thread overview] Message-ID: <bug-113736-4-NZCADh5hyS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113736-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113736 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-02-03 CC| |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- struct S { _BitInt(710) a; }; struct T { struct S b[2]; }; void foo (__seg_gs struct T *p) { struct S s; p->b[0] = s; } Bitint lowering changes here MEM <<address-space-2> _BitInt(768)> [(<address-space-2> struct T *)p_2(D)] = s_4(D); to VIEW_CONVERT_EXPR<unsigned long[12]>(MEM <<address-space-2> _BitInt(768)> [(<address-space-2> struct T *)p_2(D)])[_5] = s_7(D); accesses in a loop. Is that invalid and should have <address-space-2> also in the VCE type? Or is this just a vectorizer bug?
next prev parent reply other threads:[~2024-02-03 10:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-03 9:31 [Bug tree-optimization/113736] New: " zsojka at seznam dot cz 2024-02-03 10:25 ` jakub at gcc dot gnu.org [this message] 2024-02-03 12:24 ` [Bug tree-optimization/113736] " jakub at gcc dot gnu.org 2024-02-05 8:22 ` rguenther at suse dot de 2024-02-05 9:20 ` rguenth at gcc dot gnu.org 2024-02-05 11:25 ` jakub at gcc dot gnu.org 2024-02-06 12:00 ` cvs-commit at gcc dot gnu.org 2024-02-06 12:02 ` 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-113736-4-NZCADh5hyS@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).