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/98516] [11 Regression] Wrong code generated by tree vectorizer since r11-3823-g126ed72b9f48f853 Date: Tue, 05 Jan 2021 14:41:20 +0000 [thread overview] Message-ID: <bug-98516-4-Aa5u0tZej9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98516-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98516 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- /* { dg-do run } */ double a[4], b[2]; void __attribute__((noipa)) foo () { double a0 = a[0]; double a1 = a[1]; double a2 = a[2]; double a3 = a[3]; b[0] = a1 - a3; b[1] = a0 + a2; } int main() { a[0] = 1.; a[1] = 2.; a[2] = 3.; a[3] = 4.; foo (); if (b[0] != -2 || b[1] != 4) __builtin_abort (); return 0; }
next prev parent reply other threads:[~2021-01-05 14:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-04 17:01 [Bug tree-optimization/98516] New: Wrong code generated by tree vectorizer martin@mpa-garching.mpg.de 2021-01-04 18:59 ` [Bug tree-optimization/98516] " martin@mpa-garching.mpg.de 2021-01-05 10:30 ` [Bug tree-optimization/98516] [11 Regression] Wrong code generated by tree vectorizer since r11-3823-g126ed72b9f48f853 marxin at gcc dot gnu.org 2021-01-05 10:37 ` marxin at gcc dot gnu.org 2021-01-05 11:28 ` rguenth at gcc dot gnu.org 2021-01-05 14:33 ` rguenth at gcc dot gnu.org 2021-01-05 14:41 ` rguenth at gcc dot gnu.org [this message] 2021-01-05 16:41 ` cvs-commit at gcc dot gnu.org 2021-01-05 16:41 ` rguenth at gcc dot gnu.org 2021-01-05 18:06 ` martin@mpa-garching.mpg.de 2021-01-06 7:41 ` rguenther at suse dot de
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-98516-4-Aa5u0tZej9@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).