public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Jonathan Wakely via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
	 Jonathan Wakely <jwakely@redhat.com>,
	libstdc++ <libstdc++@gcc.gnu.org>,
	 nathan@acm.org
Subject: Re: [PATCH] testsuite: Windows paths use \ and not /
Date: Fri, 30 Sep 2022 20:23:07 +0200	[thread overview]
Message-ID: <87leq0vi0k.fsf@igel.home> (raw)
In-Reply-To: <CACb0b4=eT-4Ks0uAZHOxZSeeSahy6rXnBsWVz9b5EEN05XYwzQ@mail.gmail.com> (Jonathan Wakely via Gcc-patches's message of "Fri, 30 Sep 2022 19:04:54 +0100")

On Sep 30 2022, Jonathan Wakely via Gcc-patches wrote:

> That fixes the error, but now the regex doesn't match so there are
> still excess errors. It needs to be:
>
> // { dg-prune-output ".*\[/\\](functional|bits\[/\\]invoke.h):.*" }

In Tcl "." matches newlines, thus this will prune too much.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  parent reply	other threads:[~2022-09-30 18:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 15:38 Torbjörn SVENSSON
2022-09-30 16:26 ` Jonathan Wakely
2022-09-30 17:47   ` Jonathan Wakely
2022-09-30 17:55     ` Jakub Jelinek
2022-09-30 18:04       ` Jonathan Wakely
2022-09-30 18:07         ` Jonathan Wakely
2022-09-30 18:12           ` Jonathan Wakely
2022-09-30 21:07             ` Jonathan Wakely
2022-10-01 11:02               ` Torbjorn SVENSSON
2022-09-30 18:23         ` Andreas Schwab [this message]
2022-10-25 15:15 Torbjörn SVENSSON

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=87leq0vi0k.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=nathan@acm.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).