From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATH][_GLIBCXX_DEBUG] Fix unordered container merge
Date: Mon, 15 Nov 2021 19:16:41 +0100 [thread overview]
Message-ID: <94f3009e-4a34-2add-e2da-a2fea28e924d@gmail.com> (raw)
In-Reply-To: <CACb0b4kVD5AGwkWULiYUx3AcM-Yc4R8uLmVEDXbt9SJC_UYPWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2816 bytes --]
On 10/11/21 10:38 am, Jonathan Wakely wrote:
>
>
> On Wed, 10 Nov 2021 at 05:47, François Dumont <frs.dumont@gmail.com
> <mailto:frs.dumont@gmail.com>> wrote:
>
> On 09/11/21 5:25 pm, Jonathan Wakely wrote:
>>
>>
>> On Mon, 8 Nov 2021 at 21:36, François Dumont
>> <frs.dumont@gmail.com <mailto:frs.dumont@gmail.com>> wrote:
>>
>> Yet another version this time with only 1 guard
>> implementation. The predicate to invalidate the safe
>> iterators has been externalized.
>>
>> Ok to commit ?
>>
>>
>> I like this version a lot - thanks for persisting with it.
>>
>> OK to commit, thanks.
>>
>>
>> As an aside ...
>>
>> --- a/libstdc++-v3/testsuite/util/testsuite_abi.h
>> +++ b/libstdc++-v3/testsuite/util/testsuite_abi.h
>> @@ -24,7 +24,11 @@
>> #include <locale>
>> #if __cplusplus >= 201103L
>> # include <unordered_map>
>> +# ifdef _GLIBCXX_DEBUG
>> +namespace unord = std::_GLIBCXX_STD_C;
>> +# else
>> namespace unord = std;
>> +# endif
>> #else
>> # include <tr1/unordered_map>
>> namespace unord = std::tr1;
>>
>>
>> Several times I've been annoyed by the fact that we don't have a
>> way to refer to std::_GLIBCXX_STD_C::vector etc. that is always
>> valid, in normal mode and debug mode.
>>
>> Maybe we should add:
>>
>> namespace std { namespace _GLIBCXX_STD_C = ::std; }
>>
>> That way we can refer to std::_GLIBCXX_STD_C::foo in normal mode,
>> and it will mean the same thing as in debug mode. So we don't
>> need to use #if conditions like this.
>>
>>
> Good idea, I'll prepare it.
>
>
> Alternatively we could do this:
>
> namespace std
> {
> namespace __cxx1998 { }
> #ifdef _GLIBCXX_DEBUG
> namespace __cont = __cxx1998;
> #else
> namespace __cont = ::std::
> #endif
> }
>
> And then define this so it's always the same name:
> #define _GLIBCXX_STD_C __cont
>
> Then we can refer to std::_GLIBCXX_STD_C::vector in any context, and
> it refers to the right thing. And we could also stop using the
> SHOUTING macro, and just refer to std::__cont::vector instead.
>
> We could also make this work as std::__cxx1998::vector, but maybe we
> should move away from the "1998" name, because it doesn't make much
> sense for forward_list and unordered_map which are not in C++98.
>
Here is what I started.
I use '__normal' because when greping '__cont' in the lib it reported me
a definition of it in boost_concept_check.h. But now that I took a
closer look in this file I realize that it is just where you pick the
idea of the '__cont' !
So, what do you prefer ? __cont or __normal ?
I was not considering to replace usage of _GLIBCXX_STD_C in the lib as
long as there is no #ifdef _GLIBCXX_DEBUG. Do you prefer I do ?
François
[-- Attachment #2: normal_ns.patch --]
[-- Type: text/x-patch, Size: 2109 bytes --]
diff --git a/libstdc++-v3/include/bits/c++config b/libstdc++-v3/include/bits/c++config
index 4b7fa659300..becd83af4d9 100644
--- a/libstdc++-v3/include/bits/c++config
+++ b/libstdc++-v3/include/bits/c++config
@@ -245,6 +245,7 @@
namespace __debug { }
namespace __parallel { }
namespace __cxx1998 { }
+ namespace __normal { }
namespace __detail {
namespace __variant { } // C++17
@@ -384,6 +385,8 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
# endif
}
+ namespace __normal = __cxx1998;
+
_GLIBCXX_END_NAMESPACE_VERSION
// Inline namespace for debug mode.
@@ -407,6 +410,11 @@ _GLIBCXX_END_NAMESPACE_VERSION
# warning currently using inlined namespace mode which may fail \
without inlining due to lack of weak symbols
# endif
+#else
+namespace std
+{
+ namespace __normal = ::std;
+}
#endif
// Macros for namespace scope. Either namespace std:: or the name
diff --git a/libstdc++-v3/testsuite/23_containers/forward_list/capacity/1.cc b/libstdc++-v3/testsuite/23_containers/forward_list/capacity/1.cc
index dc2a2be3867..399064ea074 100644
--- a/libstdc++-v3/testsuite/23_containers/forward_list/capacity/1.cc
+++ b/libstdc++-v3/testsuite/23_containers/forward_list/capacity/1.cc
@@ -35,12 +35,7 @@ test01()
fld.resize(0);
VERIFY(fld.empty() == true);
-#ifdef _GLIBCXX_DEBUG
- using std::_GLIBCXX_STD_C::_Fwd_list_node;
-#else
- using std::_Fwd_list_node;
-#endif
-
+ using std::__normal::_Fwd_list_node;
std::allocator<_Fwd_list_node<double> > a;
VERIFY( fld.max_size() == __gnu_test::max_size(a) );
}
diff --git a/libstdc++-v3/testsuite/util/testsuite_abi.h b/libstdc++-v3/testsuite/util/testsuite_abi.h
index 4a0cf64f6fb..d0902db9193 100644
--- a/libstdc++-v3/testsuite/util/testsuite_abi.h
+++ b/libstdc++-v3/testsuite/util/testsuite_abi.h
@@ -24,11 +24,7 @@
#include <locale>
#if __cplusplus >= 201103L
# include <unordered_map>
-# ifdef _GLIBCXX_DEBUG
-namespace unord = std::_GLIBCXX_STD_C;
-# else
-namespace unord = std;
-# endif
+namespace unord = std::__normal;
#else
# include <tr1/unordered_map>
namespace unord = std::tr1;
next prev parent reply other threads:[~2021-11-15 18:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 17:10 François Dumont
2021-10-14 8:23 ` Jonathan Wakely
2021-10-16 13:47 ` François Dumont
2021-10-16 14:52 ` Jonathan Wakely
2021-10-21 16:51 ` François Dumont
2021-10-21 16:55 ` Jonathan Wakely
2021-10-22 5:22 ` François Dumont
2021-10-25 18:08 ` François Dumont
2021-11-06 13:51 ` François Dumont
2021-11-08 21:36 ` François Dumont
2021-11-09 16:25 ` Jonathan Wakely
2021-11-10 5:47 ` François Dumont
2021-11-10 9:38 ` Jonathan Wakely
2021-11-15 18:16 ` François Dumont [this message]
2021-11-10 11:55 ` Jonathan Wakely
2021-11-11 20:41 ` Jonathan Wakely
2021-11-11 21:33 ` François Dumont
2021-11-11 22:01 ` Jonathan Wakely
2021-11-10 0:05 ` H.J. Lu
2021-11-10 5:44 ` François Dumont
2021-11-10 7:26 ` Jonathan Wakely
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=94f3009e-4a34-2add-e2da-a2fea28e924d@gmail.com \
--to=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).