public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.martin at giref dot ulaval.ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/112477] Assignment of value-initialized iterators differs from value-initialization
Date: Tue, 09 Jan 2024 15:53:12 +0000 [thread overview]
Message-ID: <bug-112477-4-xu7HCcScfZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112477-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112477
--- Comment #5 from Dave Martin <dave.martin at giref dot ulaval.ca> ---
(In reply to Jonathan Wakely from comment #4)
> Because in C++11 any use of a singular iterator, even copying it, was
> undefined behaviour. The debug mode checks have not been properly updated to
> reflect the relaxed preconditions in more recent standards.
I'm a little confused by your response. I recently found this change in our
test suite when we updated our compilers. Our code works fine in gcc 12.3 but
returns the copy-construct error in 13.2 (as shown in the godbolt example),
both using C++17.
Are you saying the debug mode of gcc 13.2 has not been properly updated to
reflect the changes in C++17?
Because, from my understanding, gcc 13.2 added a check that restrains the
preconditions.
In other words, you seem to be saying that 13.2 was not updated to relax the
preconditions, but the behaviour I am seeing is that 13.2 added a restraint on
the preconditions.
I think the change comes from this commit:
https://github.com/gcc-mirror/gcc/commit/01b1afdc35c13cbff5cd3d37f9319285ab84b157
next prev parent reply other threads:[~2024-01-09 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 13:16 [Bug c++/112477] New: " dangelog at gmail dot com
2023-11-10 14:36 ` [Bug libstdc++/112477] " dangelog at gmail dot com
2023-12-06 14:49 ` redi at gcc dot gnu.org
2024-01-09 15:33 ` dave.martin at giref dot ulaval.ca
2024-01-09 15:37 ` redi at gcc dot gnu.org
2024-01-09 15:53 ` dave.martin at giref dot ulaval.ca [this message]
2024-01-09 16:17 ` [Bug libstdc++/112477] [13/14 Regression] " redi at gcc dot gnu.org
2024-01-09 20:06 ` dangelog at gmail dot com
2024-01-09 21:47 ` fdumont at gcc dot gnu.org
2024-01-11 17:55 ` redi at gcc dot gnu.org
2024-01-11 18:31 ` cvs-commit at gcc dot gnu.org
2024-01-11 20:55 ` cvs-commit at gcc dot gnu.org
2024-01-12 9:51 ` redi at gcc dot gnu.org
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=bug-112477-4-xu7HCcScfZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).