public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <jwakely@redhat.com>, <yvan.roux@foss.st.com>
Subject: Re: PING^2 [PATCH] testsuite: Windows paths use \ and not /
Date: Mon, 21 Nov 2022 16:38:14 +0100	[thread overview]
Message-ID: <0d1afbf1-491e-7c52-a616-809d046f466b@foss.st.com> (raw)
In-Reply-To: <237f4c26-7fd4-113c-938f-5ccb2468928a@foss.st.com>

Pushed after off-list approval from Jeff Law.

On 2022-11-17 17:44, Torbjorn SVENSSON via Gcc-patches wrote:
> Hi,
> 
> Ping, https://gcc.gnu.org/pipermail/gcc-patches/2022-November/604896.html
> 
> Ok for trunk?
> 
> Kind regards,
> Torbjörn
> 
> On 2022-11-02 19:16, Torbjorn SVENSSON wrote:
>> Hi,
>>
>> Ping, https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604312.html
>>
>> Ok for trunk?
>>
>> Kind regards,
>> Torbjörn
>>
>> On 2022-10-25 17:15, Torbjörn SVENSSON wrote:
>>> Without this patch, the following error is reported on Windows:
>>>
>>> In file included from 
>>> t:\build\arm-none-eabi\include\c++\11.3.1\string:54,
>>>                    from 
>>> t:\build\arm-none-eabi\include\c++\11.3.1\bits\locale_classes.h:40,
>>>                    from 
>>> t:\build\arm-none-eabi\include\c++\11.3.1\bits\ios_base.h:41,
>>>                    from 
>>> t:\build\arm-none-eabi\include\c++\11.3.1\ios:42,
>>>                    from 
>>> t:\build\arm-none-eabi\include\c++\11.3.1\ostream:38,
>>>                    from 
>>> t:\build\arm-none-eabi\include\c++\11.3.1\iostream:39:
>>> t:\build\arm-none-eabi\include\c++\11.3.1\bits\range_access.h:36:10: 
>>> note: include 
>>> 't:\build\arm-none-eabi\include\c++\11.3.1\initializer_list' 
>>> translated to import
>>> arm-none-eabi-g++.exe: warning: 
>>> .../gcc/testsuite/g++.dg/modules/pr99023_b.X: linker input file 
>>> unused because linking not done
>>> FAIL: g++.dg/modules/pr99023_b.X -std=c++2a  dg-regexp 6 not found: 
>>> "[^\n]*: note: include '[^\n]*/initializer_list' translated to import\n"
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>>     * g++.dg/modules/pr99023_b.X: Match Windows paths too.
>>>
>>> Co-Authored-By: Yvan ROUX <yvan.roux@foss.st.com>
>>> Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
>>> ---
>>>   gcc/testsuite/g++.dg/modules/pr99023_b.X | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/gcc/testsuite/g++.dg/modules/pr99023_b.X 
>>> b/gcc/testsuite/g++.dg/modules/pr99023_b.X
>>> index 3d82f34868b..ca5f32e5bcc 100644
>>> --- a/gcc/testsuite/g++.dg/modules/pr99023_b.X
>>> +++ b/gcc/testsuite/g++.dg/modules/pr99023_b.X
>>> @@ -3,5 +3,5 @@
>>>   // { dg-prune-output {linker input file unused} }
>>> -// { dg-regexp {[^\n]*: note: include '[^\n]*/initializer_list' 
>>> translated to import\n} }
>>> +// { dg-regexp {[^\n]*: note: include '[^\n]*[/\\]initializer_list' 
>>> translated to import\n} }
>>>   NO DO NOT COMPILE

      reply	other threads:[~2022-11-21 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 15:15 Torbjörn SVENSSON
2022-11-02 18:16 ` PING^1 " Torbjorn SVENSSON
2022-11-17 16:44   ` PING^2 " Torbjorn SVENSSON
2022-11-21 15:38     ` Torbjorn SVENSSON [this message]

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=0d1afbf1-491e-7c52-a616-809d046f466b@foss.st.com \
    --to=torbjorn.svensson@foss.st.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=yvan.roux@foss.st.com \
    /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).