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 testsuite/96109] gcc.dg/vect/slp-47.c etc. FAIL Date: Wed, 08 Jul 2020 09:18:07 +0000 [thread overview] Message-ID: <bug-96109-4-1K1kJdKL7T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96109-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96109 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2020-07-08 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, the loads should be all aligned ... but maybe we're not figuring they are. Ah, so this is confusion in vect_compute_data_ref_alignment which does /* If this is a backward running DR then first access in the larger vectype actually is N-1 elements before the address in the DR. Adjust misalign accordingly. */ if (tree_int_cst_sgn (drb->step) < 0) /* PLUS because STEP is negative. */ misalignment += ((TYPE_VECTOR_SUBPARTS (vectype) - 1) * -TREE_INT_CST_LOW (TYPE_SIZE_UNIT (TREE_TYPE (vectype)))); but that's of course not the ideal place to do this because the actual DRs alignment is _not_ different. And in fact for SLP the above is even bogus - I suppose we might even end up with wrong code in case the above would make the access appear aligned.
next prev parent reply other threads:[~2020-07-08 9:18 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 8:51 [Bug testsuite/96109] New: " ro at gcc dot gnu.org 2020-07-08 8:53 ` [Bug testsuite/96109] " ro at gcc dot gnu.org 2020-07-08 8:53 ` ro at gcc dot gnu.org 2020-07-08 9:18 ` rguenth at gcc dot gnu.org [this message] 2020-07-08 9:41 ` rguenth at gcc dot gnu.org 2020-07-10 12:26 ` clyon at gcc dot gnu.org 2021-01-19 9:11 ` [Bug testsuite/96109] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-19 9:23 ` rguenth at gcc dot gnu.org 2021-04-27 11:39 ` [Bug testsuite/96109] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2021-10-26 10:30 ` cvs-commit at gcc dot gnu.org 2021-10-26 10:30 ` [Bug testsuite/96109] [11 " rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:03 ` jakub at gcc dot gnu.org 2023-08-25 18:09 ` dcb314 at hotmail dot com 2023-08-25 18:10 ` dcb314 at hotmail dot com 2024-02-23 9:36 ` ro at gcc dot gnu.org 2024-02-23 9:37 ` ro at gcc dot gnu.org 2024-03-11 14:45 ` cvs-commit at gcc dot gnu.org 2024-03-11 14:54 ` ro 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-96109-4-1K1kJdKL7T@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).