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 testsuite/111462] [14 regression] gcc.dg/tree-ssa/ssa-sink-18.c fails after r14-4089-gd45ddc2c04e471
Date: Mon, 30 Oct 2023 10:03:31 +0000	[thread overview]
Message-ID: <bug-111462-4-sKyYsFkQV0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111462-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:ff4cea05a6e6d034eed5212109133c4b5da8520c

commit r14-5005-gff4cea05a6e6d034eed5212109133c4b5da8520c
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Oct 30 11:01:17 2023 +0100

    PR testsuite/111462 - add powerpc64le to list of ssa-sink-18.c XFAIL

            PR testsuite/111462
    gcc/testsuite/
            * gcc.dg/tree-ssa/ssa-sink-18.c: XFAIL also powerpc64le.

  parent reply	other threads:[~2023-10-30 10:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 17:49 [Bug tree-optimization/111462] New: " seurer at gcc dot gnu.org
2023-09-18 17:58 ` [Bug testsuite/111462] " pinskia at gcc dot gnu.org
2023-09-18 18:01 ` seurer at gcc dot gnu.org
2023-09-19  8:57 ` rguenth at gcc dot gnu.org
2023-09-19 13:53 ` stefansf at linux dot ibm.com
2023-09-19 14:22 ` rguenth at gcc dot gnu.org
2023-09-19 15:30 ` stefansf at linux dot ibm.com
2023-10-17 12:56 ` rguenth at gcc dot gnu.org
2023-10-25 20:31 ` seurer at gcc dot gnu.org
2023-10-30 10:01 ` rguenth at gcc dot gnu.org
2023-10-30 10:03 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-30 10:03 ` rguenth at gcc dot gnu.org
2023-11-10 14:28 ` rguenth at gcc dot gnu.org
2024-02-07 22:21 ` seurer at gcc dot gnu.org
2024-02-28 11:12 ` cvs-commit at gcc dot gnu.org
2024-02-28 11:13 ` jakub 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-111462-4-sKyYsFkQV0@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).