public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] [libstdc++] [testsuite] intro/names.cc: undef func on vxw7krn
Date: Thu, 16 Feb 2023 11:12:20 +0000 (GMT)	[thread overview]
Message-ID: <20230216111220.62FEE385781F@sourceware.org> (raw)

https://gcc.gnu.org/g:4fcf3648860af2d156a43cd18e07eeebe69cb7d3

commit 4fcf3648860af2d156a43cd18e07eeebe69cb7d3
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Feb 16 06:35:42 2023 -0300

    [libstdc++] [testsuite] intro/names.cc: undef func on vxw7krn
    
    The '#define func' added in 2021, to test that system headers don't
    violate the user namespace, exposes such a bug in the vxworks sysLib.h
    header, so add yet another such annotated workaround.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/17_intro/names.cc: Undef func on vxworks >= 7 in
            kernel mode.

Diff:
---
 libstdc++-v3/testsuite/17_intro/names.cc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libstdc++-v3/testsuite/17_intro/names.cc b/libstdc++-v3/testsuite/17_intro/names.cc
index d3e0db9bab6..c2d67ebe012 100644
--- a/libstdc++-v3/testsuite/17_intro/names.cc
+++ b/libstdc++-v3/testsuite/17_intro/names.cc
@@ -329,6 +329,8 @@
 #undef d
 #undef e
 #undef f
+// in sysLib.h, func appears as a formal parameter name
+#undef func
 #endif // __RTP__
 
 #endif // VxWorks Major >= 7

             reply	other threads:[~2023-02-16 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 11:12 Alexandre Oliva [this message]
2023-02-22 14:49 Alexandre Oliva

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=20230216111220.62FEE385781F@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).