From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
"libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: _LIBCXX_DEBUG value initialized singular iterators assert failures in std algorithms [PR104316]
Date: Thu, 21 Mar 2024 06:20:25 +0000 [thread overview]
Message-ID: <CAH6eHdQAmP1vFgAv7W2DSk65W5dG-s-iRDYPT7_e88=dtQ7GaA@mail.gmail.com> (raw)
In-Reply-To: <faa61bca-657a-4eab-b72d-f958ef5203cb@gmail.com>
On Wed, 20 Mar 2024 at 18:11, François Dumont wrote:
>
> As proposed below I also updated gcc-13 branch.
Great, thanks.
>
> libstdc++: [_GLIBCXX_DEBUG] Define __cpp_lib_null_iterators
>
> _GLIBCXX_DEBUG has now fully N3344 compliant iterator checks, we
> can define
> __cpp_lib_null_iterators macros like the normal mode.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/iterator (__cpp_lib_null_iterators): Define
> regardless of
> _GLIBCXX_DEBUG.
> * include/std/version (__cpp_lib_null_iterators): Likewise.
>
> François
>
>
> On 20/03/2024 10:02, Jonathan Wakely wrote:
> > On Wed, 20 Mar 2024 at 05:59, François Dumont wrote:
> >> Thanks to you doc:
> >>
> >> libstdc++: [_GLIBCXX_DEBUG] Define __[glibcxx,cpp_lib]_null_iterators
> >>
> >> _GLIBCXX_DEBUG has now fully N3344 compliant iterator checks, we
> >> can define
> >> __glibcxx_null_iterators and __cpp_lib_null_iterators macros like
> >> the normal
> >> mode.
> >>
> >> libstdc++-v3/ChangeLog:
> >>
> >> * version.def (null_iterators): Remove extra_cond.
> >> * version.h: Regenerate.
> >>
> >> Ok to commit ?
> > Please don't bother talking about __glibcxx_null_iterators in the
> > commit message, that's an implementation detail that always mirrors
> > the standard-defined __cpp_lib_null_iterators one. The first line of
> > the commit will be much easier to read without that.
> >
> > OK with that change, thanks.
> >
> >> I already noticed that GCC 13 has no version.h file so no backport question.
> > It has no version.h but it still has the macros:
> >
> > include/std/iterator:# define __cpp_lib_null_iterators 201304L
> > include/std/version:# define __cpp_lib_null_iterators 201304L
> >
> > Those definitions can be made to not depend on _GLIBCXX_DEBUG.
> >
next prev parent reply other threads:[~2024-03-21 6:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 20:07 _LIBCXX_DEBUG value initialized singular iterators assert failures in std algorithms Maciej Miera
2024-03-11 20:40 ` Jonathan Wakely
2024-03-12 0:54 ` Maciej Miera
2024-03-12 1:03 ` Jonathan Wakely
2024-03-12 9:52 ` Jonathan Wakely
2024-03-14 21:49 ` _LIBCXX_DEBUG value initialized singular iterators assert failures in std algorithms [PR104316] François Dumont
2024-03-16 12:16 ` François Dumont
2024-03-17 11:45 ` Jonathan Wakely
2024-03-17 16:52 ` François Dumont
2024-03-17 18:14 ` François Dumont
2024-03-18 7:45 ` Jonathan Wakely
2024-03-18 21:38 ` François Dumont
2024-03-19 9:31 ` Jonathan Wakely
2024-03-19 15:41 ` Jonathan Wakely
2024-03-20 5:59 ` François Dumont
2024-03-20 9:02 ` Jonathan Wakely
2024-03-20 18:10 ` François Dumont
2024-03-21 6:20 ` Jonathan Wakely [this message]
2024-03-18 7:45 ` 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='CAH6eHdQAmP1vFgAv7W2DSk65W5dG-s-iRDYPT7_e88=dtQ7GaA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=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).