public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code.
Date: Mon, 31 Oct 2022 03:29:01 +0000 [thread overview]
Message-ID: <bug-107451-4-qQ41Md7g9D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107451-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451
--- Comment #4 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to bartoldeman from comment #3)
> Created attachment 53786 [details]
> Corrected test case
>
> In my eagerness to make it as short as possible I made it too short indeed!
35 <bb 3> [local count: 105119324]:
36 bnd.12_91 = (unsigned int) n_29(D);
37 _90 = (long unsigned int) inc_x_33(D);
38 _89 = _90 * 8;
39 ivtmp.24_45 = (unsigned long) x_31(D);
40 ivtmp.26_3 = (unsigned long) y_32(D);
41
42 <bb 4> [local count: 955630225]:
43 # vect_dot_3_55.16_71 = PHI <vect__20.17_70(4), { 0.0, 0.0, 0.0, 0.0 }(3)>
44 # ivtmp.19_55 = PHI <ivtmp.19_92(4), 0(3)>
45 # ivtmp.24_49 = PHI <ivtmp.24_46(4), ivtmp.24_45(3)>
46 # ivtmp.26_1 = PHI <ivtmp.26_2(4), ivtmp.26_3(3)>
47 _75 = (void *) ivtmp.24_49;
48 _78 = MEM <vector(2) double> [(const double *)_75];
49 _76 = MEM <vector(2) double> [(const double *)_75 + _89 * 1];
50 vect_cst__74 = {_78, _76}; --------------- here
51 vect__4.14_73 = VEC_PERM_EXPR <vect_cst__74, vect_cst__74, { 1, 0, 1, 0
}>;
52 _5 = (void *) ivtmp.26_1;
53 _86 = MEM <vector(2) double> [(const double *)_5];
54 _84 = MEM <vector(2) double> [(const double *)_5 + _89 * 1];
55 vect_cst__82 = {_86, _84}; -------------- here
56 vect__6.13_81 = VEC_PERM_EXPR <vect_cst__82, vect_cst__82, { 0, 1, 1, 0
}>;
57 vect__20.17_70 = .FMA (vect__4.14_73, vect__6.13_81, vect_dot_3_55.16_71);
58 ivtmp.19_92 = ivtmp.19_55 + 1;
59 ivtmp.24_46 = ivtmp.24_49 + _89;
60 ivtmp.26_2 = ivtmp.26_1 + _89;
61 if (bnd.12_91 != ivtmp.19_92)
62 goto <bb 4>; [90.00%]
63 else
64 goto <bb 5>; [10.00%]
65
66 <bb 5> [local count: 105119324]:
67 _51 = .REDUC_PLUS (vect__20.17_70); [tail call]
It looks like it should be vect_cst__82 = {_84, _86} not {_86, _84}, similar
for vect_cst__74 = {_76, _78} not {_78, _76}.
next prev parent reply other threads:[~2022-10-31 3:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 19:07 [Bug tree-optimization/107451] New: " bartoldeman at users dot sourceforge.net
2022-10-28 19:19 ` [Bug tree-optimization/107451] " jakub at gcc dot gnu.org
2022-10-28 19:19 ` [Bug tree-optimization/107451] [11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-10-29 0:12 ` bartoldeman at users dot sourceforge.net
2022-10-31 3:29 ` crazylht at gmail dot com [this message]
2022-11-05 10:21 ` rguenth at gcc dot gnu.org
2022-11-05 10:29 ` [Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code since r11-6434 jakub at gcc dot gnu.org
2022-11-17 9:06 ` rguenth at gcc dot gnu.org
2022-11-17 14:48 ` rguenth at gcc dot gnu.org
2022-11-17 14:57 ` bartoldeman at users dot sourceforge.net
2022-11-17 14:58 ` rguenth at gcc dot gnu.org
2022-12-22 11:21 ` cvs-commit at gcc dot gnu.org
2022-12-22 11:21 ` [Bug tree-optimization/107451] [11/12 " rguenth at gcc dot gnu.org
2023-03-15 9:47 ` cvs-commit at gcc dot gnu.org
2023-05-02 12:03 ` [Bug tree-optimization/107451] [11 " cvs-commit at gcc dot gnu.org
2023-05-02 12:05 ` 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-107451-4-qQ41Md7g9D@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: link
Be 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).