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/108164] [12/13 Regression] wrong code with "-O3 -fno-tree-dce" on x86_64-linux-gnu since r12-5267-g540d92ae9b629eb4 Date: Mon, 19 Dec 2022 12:15:07 +0000 [thread overview] Message-ID: <bug-108164-4-SLAp2QiGNd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108164-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108164 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- We vectorize <bb 3> [local count: 955630225]: # f_33 = PHI <f_27(16), f_36(13)> f.1_1 = (unsigned short) f_33; _2 = f.1_1 + 1; f_27 = (short int) _2; if (f_27 >= -1) goto <bb 16>; [89.00%] else goto <bb 18>; [11.00%] <bb 16> [local count: 850510901]: goto <bb 3>; [100.00%] <bb 18> [local count: 105119324]: # f_94 = PHI <f_27(3)> as _70 = (unsigned short) f_36; _69 = _70 + 1; _68 = _70 + 2; _67 = _70 + 3; _66 = _70 + 4; _65 = _70 + 5; _64 = _70 + 6; _63 = _70 + 7; _62 = {_70, _69, _68, _67, _66, _65, _64, _63}; _61 = (vector(8) short int) _62; <bb 3> [local count: 567644343]: # f_33 = PHI <f_27(16), f_36(23)> # vect_vec_iv_.21_59 = PHI <_56(16), _61(23)> # ivtmp_49 = PHI <ivtmp_48(16), 0(23)> _58 = (vector(8) unsigned short) vect_vec_iv_.21_59; _57 = _58 + { 8, 8, 8, 8, 8, 8, 8, 8 }; _56 = (vector(8) short int) _57; vect_f.22_55 = VIEW_CONVERT_EXPR<vector(8) unsigned short>(vect_vec_iv_.21_59); f.1_1 = (unsigned short) f_33; vect__2.23_53 = vect_f.22_55 + { 1, 1, 1, 1, 1, 1, 1, 1 }; _2 = f.1_1 + 1; vect_f_27.24_52 = VIEW_CONVERT_EXPR<vector(8) short int>(vect__2.23_53); f_27 = (short int) _2; ivtmp_48 = ivtmp_49 + 1; if (ivtmp_48 < bnd.18_75) goto <bb 16>; [83.33%] else goto <bb 25>; [16.67%] <bb 16> [local count: 473036953]: goto <bb 3>; [100.00%] <bb 25> [local count: 94607391]: # vect_f_27.24_51 = PHI <vect_f_27.24_52(3)> _50 = BIT_FIELD_REF <vect_f_27.24_51, 16, 112>; that looks wrong.
next prev parent reply other threads:[~2022-12-19 12:15 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-18 14:36 [Bug tree-optimization/108164] New: wrong code with "-O3 -fno-tree-dce" on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2022-12-18 17:37 ` [Bug tree-optimization/108164] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-12-18 17:41 ` pinskia at gcc dot gnu.org 2022-12-18 17:42 ` pinskia at gcc dot gnu.org 2022-12-19 8:15 ` rguenth at gcc dot gnu.org 2022-12-19 8:40 ` [Bug tree-optimization/108164] [12/13 Regression] wrong code with "-O3 -fno-tree-dce" on x86_64-linux-gnu since r12-5267-g540d92ae9b629eb4 marxin at gcc dot gnu.org 2022-12-19 8:54 ` rguenth at gcc dot gnu.org 2022-12-19 12:15 ` rguenth at gcc dot gnu.org [this message] 2022-12-19 13:53 ` rguenth at gcc dot gnu.org 2022-12-19 15:36 ` cvs-commit at gcc dot gnu.org 2022-12-19 15:37 ` [Bug tree-optimization/108164] [12 " rguenth at gcc dot gnu.org 2023-01-24 14:27 ` cvs-commit at gcc dot gnu.org 2023-01-24 14:28 ` 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-108164-4-SLAp2QiGNd@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).