public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <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: Fri, 28 Oct 2022 19:19:44 +0000 [thread overview] Message-ID: <bug-107451-4-ekeIHqq8Ap@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |10.4.0 Status|RESOLVED |NEW Target Milestone|--- |11.4 Last reconfirmed| |2022-10-28 Summary|Segmentation fault with |[11/12/13 Regression] |vectorized code. |Segmentation fault with | |vectorized code. Resolution|INVALID |--- Ever confirmed|0 |1 Known to fail| |11.1.0 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I think this code is undefined as x/y are arrays of size 1 but you access one past. But here is the main which makes this well defined: int main(void) { double x[2] = {0,0}, y[2] = {0,0}; return dot(1, &x[0], 4096*4096, &y[0]); } Still an issue on the trunk. Confirmed.
next prev parent reply other threads:[~2022-10-28 19:19 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 ` pinskia at gcc dot gnu.org [this message] 2022-10-29 0:12 ` [Bug tree-optimization/107451] [11/12/13 Regression] " bartoldeman at users dot sourceforge.net 2022-10-31 3:29 ` crazylht at gmail dot com 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-ekeIHqq8Ap@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).