From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][_GLIBCXX_DEBUG] Fix std::__niter_base behavior
Date: Wed, 14 Feb 2024 22:48:12 +0100 [thread overview]
Message-ID: <e2e0e79a-a416-45a4-8895-4e9ffc4b5686@gmail.com> (raw)
In-Reply-To: <CACb0b4nbX5fPL=G7S8hDSne37Rga5MsGaUC7VN759ypuKJYGUQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1956 bytes --]
On 14/02/2024 20:44, Jonathan Wakely wrote:
>
>
> On Wed, 14 Feb 2024 at 18:39, François Dumont <frs.dumont@gmail.com>
> wrote:
>
> libstdc++: [_GLIBCXX_DEBUG] Fix std::__niter_base behavior
>
> std::__niter_base is used in _GLIBCXX_DEBUG mode to remove
> _Safe_iterator<>
> wrapper on random access iterators. But doing so it should also
> preserve
> original
> behavior to remove __normal_iterator wrapper.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/stl_algobase.h (std::__niter_base): Redefine the
> overload
> definitions for __gnu_debug::_Safe_iterator.
> * include/debug/safe_iterator.tcc (std::__niter_base): Adapt
> declarations.
>
> Ok to commit once all tests completed (still need to check
> pre-c++11) ?
>
>
>
> The declaration in include/bits/stl_algobase.h has a
> noexcept-specifier but the definition in
> include/debug/safe_iterator.tcc does not have one - that seems wrong
> (I'm surprised it even compiles).
It does ! I thought it was only necessary at declaration, and I also had
troubles doing it right at definition because of the interaction with
the auto and ->. Now simplified and consistent in this new proposal.
> Just using std::is_nothrow_copy_constructible<_Ite> seems simpler,
> that will be true for __normal_iterator<I, C> if
> is_nothrow_copy_constructible<I> is true.
>
Ok
> The definition in include/debug/safe_iterator.tcc should use
> std::declval<_Ite>() not declval<_Ite>(). Is there any reason why the
> definition uses a late-specified-return-type (i.e. auto and ->) when
> the declaration doesn't?
>
>
I initially plan to use '->
std::decltype(std::__niter_base(__it.base()))' but this did not compile,
ambiguity issue. So I resort to using std::declval and I could have then
done it the same way as declaration, done now.
Attached is what I'm testing, ok to commit once fully tested ?
François
[-- Attachment #2: niter_base_patch.txt --]
[-- Type: text/plain, Size: 2658 bytes --]
diff --git a/libstdc++-v3/include/bits/stl_algobase.h b/libstdc++-v3/include/bits/stl_algobase.h
index e7207f67266..0f73da13172 100644
--- a/libstdc++-v3/include/bits/stl_algobase.h
+++ b/libstdc++-v3/include/bits/stl_algobase.h
@@ -317,12 +317,26 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
_GLIBCXX_NOEXCEPT_IF(std::is_nothrow_copy_constructible<_Iterator>::value)
{ return __it; }
+#if __cplusplus < 201103L
template<typename _Ite, typename _Seq>
- _GLIBCXX20_CONSTEXPR
_Ite
__niter_base(const ::__gnu_debug::_Safe_iterator<_Ite, _Seq,
std::random_access_iterator_tag>&);
+ template<typename _Ite, typename _Cont, typename _Seq>
+ _Ite
+ __niter_base(const ::__gnu_debug::_Safe_iterator<
+ ::__gnu_cxx::__normal_iterator<_Ite, _Cont>, _Seq,
+ std::random_access_iterator_tag>&);
+#else
+ template<typename _Ite, typename _Seq>
+ _GLIBCXX20_CONSTEXPR
+ decltype(std::__niter_base(std::declval<_Ite>()))
+ __niter_base(const ::__gnu_debug::_Safe_iterator<_Ite, _Seq,
+ std::random_access_iterator_tag>&)
+ noexcept(std::is_nothrow_copy_constructible<_Ite>::value);
+#endif
+
// Reverse the __niter_base transformation to get a
// __normal_iterator back again (this assumes that __normal_iterator
// is only used to wrap random access iterators, like pointers).
diff --git a/libstdc++-v3/include/debug/safe_iterator.tcc b/libstdc++-v3/include/debug/safe_iterator.tcc
index 6eb70cbda04..a8b24233e85 100644
--- a/libstdc++-v3/include/debug/safe_iterator.tcc
+++ b/libstdc++-v3/include/debug/safe_iterator.tcc
@@ -235,13 +235,29 @@ namespace std _GLIBCXX_VISIBILITY(default)
{
_GLIBCXX_BEGIN_NAMESPACE_VERSION
+#if __cplusplus < 201103L
template<typename _Ite, typename _Seq>
- _GLIBCXX20_CONSTEXPR
_Ite
__niter_base(const ::__gnu_debug::_Safe_iterator<_Ite, _Seq,
std::random_access_iterator_tag>& __it)
{ return __it.base(); }
+ template<typename _Ite, typename _Cont, typename _DbgSeq>
+ _Ite
+ __niter_base(const ::__gnu_debug::_Safe_iterator<
+ ::__gnu_cxx::__normal_iterator<_Ite, _Cont>, _DbgSeq,
+ std::random_access_iterator_tag>& __it)
+ { return __it.base().base(); }
+#else
+ template<typename _Ite, typename _Seq>
+ _GLIBCXX20_CONSTEXPR
+ decltype(std::__niter_base(std::declval<_Ite>()))
+ __niter_base(const ::__gnu_debug::_Safe_iterator<_Ite, _Seq,
+ std::random_access_iterator_tag>& __it)
+ noexcept(std::is_nothrow_copy_constructible<_Ite>::value)
+ { return std::__niter_base(__it.base()); }
+#endif
+
template<bool _IsMove,
typename _Ite, typename _Seq, typename _Cat, typename _OI>
_GLIBCXX20_CONSTEXPR
next prev parent reply other threads:[~2024-02-14 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 18:39 François Dumont
2024-02-14 19:44 ` Jonathan Wakely
2024-02-14 21:48 ` François Dumont [this message]
2024-02-15 13:17 ` Jonathan Wakely
2024-02-15 18:38 ` François Dumont
2024-02-15 18:40 ` Jonathan Wakely
2024-02-17 14:14 ` François Dumont
2024-02-19 7:07 ` Stephan Bergmann
2024-02-19 8:12 ` Jonathan Wakely
2024-02-19 8:21 ` Jonathan Wakely
2024-02-19 18:39 ` François Dumont
2024-02-20 18:42 ` François Dumont
2024-02-20 19:27 ` 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=e2e0e79a-a416-45a4-8895-4e9ffc4b5686@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).