public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115640] GCN: FAIL: gfortran.dg/vect/pr115528.f -O execution test Date: Tue, 25 Jun 2024 11:56:03 +0000 [thread overview] Message-ID: <bug-115640-4-eNNcacm6WA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115640-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115640 --- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- For GCN target (tested '-march=gfx908'), we've got identical code ('pr115528.exe') before vs. after the commit r15-1582-g2f83ea87ee328d337f87d4430861221be9babe1e "tree-optimization/115528 - fix vect alignment analysis for outer loop vect" code changes, so it's likely an unrelated issue?
next prev parent reply other threads:[~2024-06-25 11:56 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-25 11:39 [Bug target/115640] New: " tschwinge at gcc dot gnu.org 2024-06-25 11:56 ` tschwinge at gcc dot gnu.org [this message] 2024-06-25 12:30 ` [Bug target/115640] " rguenth at gcc dot gnu.org 2024-06-25 12:36 ` ams at gcc dot gnu.org 2024-06-25 13:08 ` rguenther at suse dot de 2024-06-25 17:55 ` [Bug target/115640] [15 Regression] " tschwinge at gcc dot gnu.org 2024-06-26 6:38 ` rguenther at suse dot de 2024-06-26 7:40 ` rguenth at gcc dot gnu.org 2024-06-26 11:05 ` rguenth at gcc dot gnu.org 2024-06-26 11:06 ` rguenth at gcc dot gnu.org 2024-06-26 11:06 ` rguenth at gcc dot gnu.org 2024-06-26 11:30 ` ams at gcc dot gnu.org 2024-06-26 11:54 ` tschwinge at gcc dot gnu.org 2024-06-26 12:26 ` rguenth at gcc dot gnu.org 2024-06-26 12:34 ` rguenth at gcc dot gnu.org 2024-06-26 13:34 ` ams at gcc dot gnu.org 2024-06-26 13:41 ` rguenther at suse dot de 2024-06-26 14:05 ` ams at gcc dot gnu.org 2024-06-28 11:08 ` cvs-commit at gcc dot gnu.org 2024-06-28 11:12 ` ams at gcc dot gnu.org 2024-06-28 11:44 ` cvs-commit at gcc dot gnu.org 2024-06-28 11:45 ` 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-115640-4-eNNcacm6WA@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).