public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
	Iain Sandoe <iains.gcc@gmail.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++, testsuite: Add a prune expression for external tool bug.
Date: Fri, 19 Nov 2021 17:54:04 +0000	[thread overview]
Message-ID: <CAH6eHdQGcWrDAfeTYGXfwZWs0D48VRO7078JKKcvCYKGocGjCA@mail.gmail.com> (raw)
In-Reply-To: <20211119160246.48711-1-iain@sandoe.co.uk>

On Fri, 19 Nov 2021 at 16:04, Iain Sandoe via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Depending on the permutation of CPU, OS version and shared/non-
> shared library inclusion, we get can get warnings from the external
> tools (ld64, dsymutil) which are not actually libstdc++ issues but
> relate to the external tools themselves.  This is already pruned
> in the main testsuite, this adds it to the library.
>
> tested on x86_64, i686 darwin17 which is one of the platforms where
> the issue shows.
>
> OK for master? / eventual backports ?

Yes, thanks.

      reply	other threads:[~2021-11-19 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 16:02 Iain Sandoe
2021-11-19 17:54 ` Jonathan Wakely [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=CAH6eHdQGcWrDAfeTYGXfwZWs0D48VRO7078JKKcvCYKGocGjCA@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=iains.gcc@gmail.com \
    --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).