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/108692] [11/12/13 Regression] Miscompilation of orc_test.c since r11-5160 Date: Tue, 07 Feb 2023 11:45:59 +0000 [thread overview] Message-ID: <bug-108692-4-Rhbnr8rWmc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108692-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108692 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Before the r11-5160 change, the innermost loop was an unsigned char x 16 -> int x 4 SAD_EXPR: <bb 7> [local count: 567644343]: # vect_var12_i_49.13_90 = PHI <vect_patt_46.22_103(7), { 0, 0, 0, 0 }(6)> # ivtmp.57_149 = PHI <ivtmp.57_150(7), 0(6)> vect_var32_32.16_95 = MEM <const vector(16) signed char> [(const signed char *)vectp.15_91 + ivtmp.57_149 * 1]; vect_var33_33.19_100 = MEM <const vector(16) signed char> [(const signed char *)vectp.18_96 + ivtmp.57_149 * 1]; vect_var32.20_101 = VIEW_CONVERT_EXPR<vector(16) unsigned char>(vect_var32_32.16_95); vect_var33.21_102 = VIEW_CONVERT_EXPR<vector(16) unsigned char>(vect_var33_33.19_100); vect_patt_46.22_103 = SAD_EXPR <vect_var32.20_101, vect_var33.21_102, vect_var12_i_49.13_90>; ivtmp.57_150 = ivtmp.57_149 + 16; if (ivtmp.57_150 != _166) goto <bb 7>; [83.33%] else goto <bb 10>; [16.67%] with vect_patt_46.22_103/vect_var12_i_49.13_90 type being vector(4) int. After the change it is signed char x 16 -> int x 4 SAD_EXPR instead: <bb 7> [local count: 567644343]: # vect_var12_i_49.13_99 = PHI <vect_patt_39.20_110(7), { 0, 0, 0, 0 }(6)> # ivtmp.55_156 = PHI <ivtmp.55_157(7), 0(6)> vect_var32_32.16_104 = MEM <const vector(16) signed char> [(const signed char *)vectp.15_100 + ivtmp.55_156 * 1]; vect_var33_33.19_109 = MEM <const vector(16) signed char> [(const signed char *)vectp.18_105 + ivtmp.55_156 * 1]; vect_patt_39.20_110 = SAD_EXPR <vect_var32_32.16_104, vect_var33_33.19_109, vect_var12_i_49.13_99>; ivtmp.55_157 = ivtmp.55_156 + 16; if (ivtmp.55_157 != _173) goto <bb 7>; [83.33%] else goto <bb 10>; [16.67%]
next prev parent reply other threads:[~2023-02-07 11:45 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-07 11:23 [Bug tree-optimization/108692] New: " jakub at gcc dot gnu.org 2023-02-07 11:24 ` [Bug tree-optimization/108692] " jakub at gcc dot gnu.org 2023-02-07 11:45 ` jakub at gcc dot gnu.org [this message] 2023-02-07 13:40 ` jakub at gcc dot gnu.org 2023-02-07 14:12 ` jakub at gcc dot gnu.org 2023-02-07 14:53 ` jakub at gcc dot gnu.org 2023-02-08 17:44 ` cvs-commit at gcc dot gnu.org 2023-02-08 17:44 ` [Bug tree-optimization/108692] [11/12 " jakub at gcc dot gnu.org 2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org 2023-02-10 18:02 ` [Bug tree-optimization/108692] [11 " jakub at gcc dot gnu.org 2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org 2023-05-03 10:38 ` 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-108692-4-Rhbnr8rWmc@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).