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/108723] [13 Regression] Recent changes broke risc-v testsuite
Date: Tue, 14 Feb 2023 10:27:32 +0000	[thread overview]
Message-ID: <bug-108723-4-VbGZcHfPpK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108723-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andreas Schwab <schwab@gcc.gnu.org>:

https://gcc.gnu.org/g:26f4b055d97804666d6d144b2af9b9dee0854354

commit r13-5981-g26f4b055d97804666d6d144b2af9b9dee0854354
Author: Andreas Schwab <schwab@suse.de>
Date:   Thu Feb 9 10:40:39 2023 +0100

    testsuite: adjust patterns in RISC-V tests to skip unwind table directives

    gcc/testsuite/
            PR target/108723
            * gcc.target/riscv/shorten-memrefs-1.c: Adjust patterns to skip
            over cfi directives.
            * gcc.target/riscv/shorten-memrefs-2.c: Likewise.
            * gcc.target/riscv/shorten-memrefs-3.c: Likewise.
            * gcc.target/riscv/shorten-memrefs-4.c: Likewise.
            * gcc.target/riscv/shorten-memrefs-5.c: Likewise.
            * gcc.target/riscv/shorten-memrefs-6.c: Likewise.
            * gcc.target/riscv/shorten-memrefs-8.c: Likewise.

  parent reply	other threads:[~2023-02-14 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 19:01 [Bug testsuite/108723] New: " law at gcc dot gnu.org
2023-02-09 13:43 ` [Bug testsuite/108723] " rguenth at gcc dot gnu.org
2023-02-14 10:27 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-14 10:28 ` schwab@linux-m68k.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-108723-4-VbGZcHfPpK@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).