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 d/94315] [10 regression] new tests gdc.dg/pr93038.d and gdc.dg/pr93038b.d in r10-7320 fail
Date: Wed, 01 Apr 2020 21:43:01 +0000 [thread overview]
Message-ID: <bug-94315-4-cDK2dIpE6W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94315-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94315
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>:
https://gcc.gnu.org/g:918b89b7623b6c42b09f37b7e3ef807d1abbabb8
commit r10-7505-g918b89b7623b6c42b09f37b7e3ef807d1abbabb8
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date: Wed Apr 1 23:37:06 2020 +0200
d: Fix new tests gdc.dg/pr93038.d and gdc.dg/pr93038b.d in r10-7320 fail
The scan-file match is likely too strict to always succeed, so instead
have split it up into a set of smaller matches.
gcc/testsuite/ChangeLog:
PR d/94315
* gdc.dg/pr93038.d: Split dg-final into multiple tests.
* gdc.dg/pr93038b.d: Likewise.
next prev parent reply other threads:[~2020-04-01 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 1:50 [Bug d/94315] New: " seurer at linux dot vnet.ibm.com
2020-03-25 7:55 ` [Bug d/94315] " rguenth at gcc dot gnu.org
2020-03-25 10:16 ` marxin at gcc dot gnu.org
2020-03-25 15:56 ` law at redhat dot com
2020-04-01 17:46 ` ibuclaw at gdcproject dot org
2020-04-01 21:43 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-01 21:47 ` ibuclaw at gdcproject dot org
2020-04-02 20:17 ` seurer at linux dot vnet.ibm.com
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-94315-4-cDK2dIpE6W@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).