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 rtl-optimization/95493] [10 Regression] test for vector members apparently reordered with assignment to vector members since r10-7523-gb90061c6ec090c6b
Date: Tue, 16 Jun 2020 22:15:10 +0000	[thread overview]
Message-ID: <bug-95493-4-RsvBztjLFn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95493-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r11-1408-gd4b0f996fc497fba8724960107c3b52d3011c117
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jun 16 23:14:23 2020 +0100

    middle-end: Add another testcase for PR 95493

    This was reported on the gcc-help mailing list. The regression started
    with r10-589 and was fixed by r11-963.

    gcc/testsuite/ChangeLog:

            * g++.dg/torture/pr95493-1.C: New test.

  parent reply	other threads:[~2020-06-16 22:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  7:49 [Bug tree-optimization/95493] New: [10 Regression] test for vector members apparently reordered with assignment to vector members kretz at kde dot org
2020-06-03  8:15 ` [Bug tree-optimization/95493] [10/11 Regression] test for vector members apparently reordered with assignment to vector members since r10-7523-gb90061c6ec090c6b marxin at gcc dot gnu.org
2020-06-03  8:20 ` [Bug middle-end/95493] " pinskia at gcc dot gnu.org
2020-06-03  9:51 ` [Bug rtl-optimization/95493] " rguenth at gcc dot gnu.org
2020-06-03 10:00 ` rguenth at gcc dot gnu.org
2020-06-03 11:15 ` rguenth at gcc dot gnu.org
2020-06-05  6:35 ` cvs-commit at gcc dot gnu.org
2020-06-05  6:36 ` [Bug rtl-optimization/95493] [10 " rguenth at gcc dot gnu.org
2020-06-16 11:57 ` rguenth at gcc dot gnu.org
2020-06-16 12:58 ` redi at gcc dot gnu.org
2020-06-16 22:15 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-19 12:08 ` kretz at kde dot org
2020-06-19 12:29 ` rguenth at gcc dot gnu.org
2020-06-23 13:31 ` cvs-commit at gcc dot gnu.org
2020-06-23 13:31 ` 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-95493-4-RsvBztjLFn@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).