public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "François Dumont" <frs.dumont@gmail.com>
To: gcc@gcc.gnu.org, libstdc++ <libstdc++@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix coroutine tests for libstdc++ gnu-version-namespace mode
Date: Mon, 2 Oct 2023 19:07:02 +0200	[thread overview]
Message-ID: <e3dfc20d-de5e-d1de-b1bb-aa54b8fb8b7c@gmail.com> (raw)
In-Reply-To: <4ebb6936-d652-84a5-0028-6ca0a5d2d238@gmail.com>

Hi

Gentle reminder for this minor patch.

Thanks

On 23/09/2023 22:10, François Dumont wrote:
> I'm eventually fixing those tests the same way we manage this problem 
> in libstdc++ testsuite.
>
>    testsuite: Add optional libstdc++ version namespace in expected 
> diagnostic
>
>     When libstdc++ is build with 
> --enable-symvers=gnu-versioned-namespace diagnostics are
>     showing this namespace, currently __8.
>
>     gcc/testsuite/ChangeLog:
>
>             * 
> testsuite/g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C: Add optional
>             '__8' version namespace in expected diagnostic.
>             * 
> testsuite/g++.dg/coroutines/coro-bad-alloc-01-bad-op-del.C: Likewise.
>             * 
> testsuite/g++.dg/coroutines/coro-bad-alloc-02-no-op-new-nt.C: Likewise.
>             * 
> testsuite/g++.dg/coroutines/coro-bad-grooaf-01-grooaf-expected.C: 
> Likewise.
>             * testsuite/g++.dg/coroutines/pr97438.C: Likewise.
>             * testsuite/g++.dg/coroutines/ramp-return-b.C: Likewise.
>
> Tested under Linux x86_64.
>
> I'm contributing to libstdc++ so I already have write access.
>
> Ok to commit ?
>
> François

  reply	other threads:[~2023-10-02 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 20:10 François Dumont
2023-10-02 17:07 ` François Dumont [this message]
2023-10-03  9:52   ` Jonathan Wakely
2023-10-03 20:14     ` François Dumont
2023-10-08 13:59 ` Iain Sandoe
2023-10-11  4:49   ` François Dumont
2023-10-11  7:30     ` Iain Sandoe
2023-10-11 17:22       ` François Dumont

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=e3dfc20d-de5e-d1de-b1bb-aa54b8fb8b7c@gmail.com \
    --to=frs.dumont@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@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).