public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: libstdc++ <libstdc++@gcc.gnu.org>, GCC-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++, testsuite, Darwin : Adjust for names used in system headers.
Date: Mon, 15 Mar 2021 12:20:54 +0000	[thread overview]
Message-ID: <20210315122054.GN3008@redhat.com> (raw)
In-Reply-To: <11F9966D-6E1E-4B7E-B714-76EED90D6173@sandoe.co.uk>

On 15/03/21 00:40 +0000, Iain Sandoe wrote:
>Hi,
>
>What is slightly odd here is that this problem shows up for
>installed testing, but not when the test-suite is run in-tree.
>
>However, the issue is clear (and doesn’t need to depend on
>figuring out why it doesn’t show in-tree).
>
>tested on powerpc-darwin9, x86_64-darwin
>
>OK for master?
>thanks
>Iain
>
>====
>
>For all current Darwin SDKs inttypes.h has:
>extern intmax_t imaxabs(intmax_t j);
>
>So we need to exclude j from the defined symbol starts.
>
>libstdc++-v3/ChangeLog:
>
>	* testsuite/17_intro/names.cc: Exclude j from the list
>	of symbol starts on Darwin platform.

OK with adjusted changelog as discussed on IRC, thanks.


> libstdc++-v3/testsuite/17_intro/names.cc | 5 +++++
> 1 file changed, 5 insertions(+)
>
>diff --git a/libstdc++-v3/testsuite/17_intro/names.cc b/libstdc++-v3/testsuite/17_intro/names.cc
>index 4534d790772..624e3ed9ccf 100644
>--- a/libstdc++-v3/testsuite/17_intro/names.cc
>+++ b/libstdc++-v3/testsuite/17_intro/names.cc
>@@ -197,6 +197,11 @@
> #undef v
> #endif
>
>+#ifdef __APPLE__
>+// inttypes.h:  extern intmax_t imaxabs(intmax_t j);
>+#undef j
>+#endif
>+
> #ifdef __hpux__
> #undef d
> #undef r
>-- 
>2.24.1
>
>


      reply	other threads:[~2021-03-15 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  0:40 Iain Sandoe
2021-03-15 12:20 ` 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=20210315122054.GN3008@redhat.com \
    --to=jwakely@redhat.com \
    --cc=GCC-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --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).