public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97494] [11 regression] several vector test case failures starting with r11-3966
Date: Thu, 11 Mar 2021 13:05:53 +0000	[thread overview]
Message-ID: <bug-97494-4-BaJbvDMHS8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97494-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97494

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:f6c1d026c3a9109de58d1148e3f54b5273ebb86a

commit r11-7621-gf6c1d026c3a9109de58d1148e3f54b5273ebb86a
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Mar 11 14:03:55 2021 +0100

    testsuite/97494 - XFAIL gcc.dg/vect/vect-complex-5.c on !vect_hw_misalign

    This is a missed optimization due to bogus alignment analysis.

    2021-03-11  Richard Biener  <rguenther@suse.de>

            PR testsuite/97494
            * gcc.dg/vect/vect-complex-5.c: XFAIL on !vect_hw_misalign.

  parent reply	other threads:[~2021-03-11 13:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 15:07 [Bug tree-optimization/97494] New: " seurer at gcc dot gnu.org
2020-10-19 15:21 ` [Bug tree-optimization/97494] " rguenth at gcc dot gnu.org
2020-10-21  9:18 ` clyon at gcc dot gnu.org
2020-12-11 12:15 ` ro at gcc dot gnu.org
2021-01-14  9:27 ` rguenth at gcc dot gnu.org
2021-01-18 14:00 ` rguenth at gcc dot gnu.org
2021-01-18 14:19 ` rguenth at gcc dot gnu.org
2021-01-18 14:20 ` cvs-commit at gcc dot gnu.org
2021-03-11 12:32 ` cvs-commit at gcc dot gnu.org
2021-03-11 13:03 ` rguenth at gcc dot gnu.org
2021-03-11 13:05 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-11 13:13 ` cvs-commit at gcc dot gnu.org
2021-03-11 13:16 ` rguenth at gcc dot gnu.org
2021-03-11 18:48 ` seurer 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-97494-4-BaJbvDMHS8@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).