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 tree-optimization/109735] [14 Regression] ICE in vectorizable_store, at tree-vect-stmts.cc:8529 since r14-322-g821ef93976e750 Date: Fri, 05 May 2023 06:54:21 +0000 [thread overview] Message-ID: <bug-109735-4-K0W7DM8PYL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109735-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109735 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- We have a sign mismatch here from vectorizing a POINTER_MINUS_EXPR. (gdb) p debug ((slp_tree)0x39c2970) pr83329.c:11:6: note: node 0x39c2970 (max_nunits=1, refcnt=1) vector(1) int pr83329.c:11:6: note: op template: _2 = &g - &f; pr83329.c:11:6: note: stmt 0 _2 = &g - &f; pr83329.c:11:6: note: stmt 1 _3 = &e - &f; pr83329.c:11:6: note: children 0x39c2a00 0x39c2a90 but (gdb) p debug_gimple_stmt (0x7ffff6fc3dc0) _24 = VIEW_CONVERT_EXPR<vector(1) unsigned int>(_23); there's code to handle this but it's conditional on a special case. The fix is to invoke it generally I think.
next prev parent reply other threads:[~2023-05-05 6:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-04 14:06 [Bug tree-optimization/109735] New: " marxin at gcc dot gnu.org 2023-05-04 14:06 ` [Bug tree-optimization/109735] " marxin at gcc dot gnu.org 2023-05-05 6:16 ` rguenth at gcc dot gnu.org 2023-05-05 6:54 ` rguenth at gcc dot gnu.org [this message] 2023-05-05 12:19 ` cvs-commit at gcc dot gnu.org 2023-05-05 12:19 ` rguenth 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-109735-4-K0W7DM8PYL@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).