public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@adacore.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "François Dumont" <frs.dumont@gmail.com>,
	"Jonathan Wakely" <jwakely.gcc@gmail.com>,
	libstdc++ <libstdc++@gcc.gnu.org>
Subject: [PATCH] libstdc++: bvector: undef always_inline macro
Date: Thu, 09 Nov 2023 16:49:37 -0300	[thread overview]
Message-ID: <orr0kypuzy.fsf_-_@lxoliva.fsfla.org> (raw)
In-Reply-To: <CACb0b4mXrW0L7cpynt=BRJbEemW+UnDfXi84DYZHcyPUWZ6HuA@mail.gmail.com> (Jonathan Wakely's message of "Thu, 9 Nov 2023 08:16:12 +0000")

On Nov  9, 2023, Jonathan Wakely <jwakely@redhat.com> wrote:

> But I've just realised we probably want to #undef the macro at the end
> of bits/stl_bvector.h too.

I'm not sure why (what if another libstdc++ header were to define the
macro, includes stl_bvector.h, and then use the macro expecting it to
still be there?), but I suppose this is what you mean.  Regstrapped on
x86_64-linux-gnu just to be sure.  Ok to install?


From: Alexandre Oliva <oliva@adacore.com>

It's customary to undefine temporary internal macros at the end of the
header that defines them, even such widely-usable ones as
_GLIBCXX_ALWAYS_INLINE, so do so in the header where the define was
recently introduced.


for  libstdc++-v3/ChangeLog

	* include/bits/stl_bvector.h (_GLIBCXX_ALWAYS_INLINE): Undef.
---
 libstdc++-v3/include/bits/stl_bvector.h |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/libstdc++-v3/include/bits/stl_bvector.h b/libstdc++-v3/include/bits/stl_bvector.h
index 2b91af2005f2d..1b7648535c523 100644
--- a/libstdc++-v3/include/bits/stl_bvector.h
+++ b/libstdc++-v3/include/bits/stl_bvector.h
@@ -1628,4 +1628,6 @@ _GLIBCXX_END_NAMESPACE_CONTAINER
 _GLIBCXX_END_NAMESPACE_VERSION
 } // namespace std
 
+#undef _GLIBCXX_ALWAYS_INLINE
+
 #endif

-- 
Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
   Free Software Activist                   GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive

  reply	other threads:[~2023-11-09 19:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 16:10 [PATCH] libstdc++: optimize bit iterators assuming normalization [PR110807] Alexandre Oliva
2023-11-08 19:32 ` Jonathan Wakely
2023-11-09  1:17   ` [PATCH v2] " Alexandre Oliva
2023-11-09  1:22     ` Jonathan Wakely
2023-11-09  3:36       ` [PATCH v3] " Alexandre Oliva
2023-11-09  5:57         ` François Dumont
2023-11-09  8:16           ` Jonathan Wakely
2023-11-09 19:49             ` Alexandre Oliva [this message]
2023-11-09 20:18               ` [PATCH] libstdc++: bvector: undef always_inline macro Jonathan Wakely
2023-11-15  2:20                 ` Patrick Palka
2023-11-15  5:53                   ` Alexandre Oliva
2023-11-15  2:44                 ` Alexandre Oliva
2023-11-15  5:08                   ` Alexandre Oliva
2023-11-15  8:22                   ` Jonathan Wakely
2023-11-16  4:40                     ` Alexandre Oliva
2024-02-07 16:25       ` [PATCH v2] libstdc++: optimize bit iterators assuming normalization [PR110807] Torbjorn SVENSSON
2024-02-07 16:36         ` Jonathan Wakely
2024-02-09  8:49           ` Torbjorn SVENSSON

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=orr0kypuzy.fsf_-_@lxoliva.fsfla.org \
    --to=oliva@adacore.com \
    --cc=frs.dumont@gmail.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=jwakely@redhat.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).