public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/114367] std::vector<bool> constexpr initialization doesn't start lifetime of array members
Date: Wed, 03 Apr 2024 10:46:40 +0000	[thread overview]
Message-ID: <bug-114367-4-TxDfUavz03@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114367-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114367

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:d8d71b19f0b1e28fd6d413a6874ec55c568865b0

commit r13-8568-gd8d71b19f0b1e28fd6d413a6874ec55c568865b0
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Mar 18 13:00:17 2024 +0000

    libstdc++: Begin lifetime of storage in std::vector<bool> [PR114367]

    This doesn't cause a problem with GCC, but Clang correctly diagnoses a
    bug in the code. The objects in the allocated storage need to begin
    their lifetime before we start using them.

    This change uses the allocator's construct function instead of using
    std::construct_at directly, in order to support fancy pointers.

    libstdc++-v3/ChangeLog:

            PR libstdc++/114367
            * include/bits/stl_bvector.h (_M_allocate): Use allocator's
            construct function to begin lifetime of words.

    (cherry picked from commit 16afbd9c9c4282d56062cef95e6eccfdcf3efe03)

  parent reply	other threads:[~2024-04-03 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 21:50 [Bug libstdc++/114367] New: " teodor_spaeren at riseup dot net
2024-03-16 22:13 ` [Bug libstdc++/114367] " pinskia at gcc dot gnu.org
2024-03-16 22:14 ` pinskia at gcc dot gnu.org
2024-03-17  9:15 ` redi at gcc dot gnu.org
2024-03-18 13:19 ` redi at gcc dot gnu.org
2024-03-19 15:14 ` cvs-commit at gcc dot gnu.org
2024-04-03 10:46 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-11 17:06 ` cvs-commit at gcc dot gnu.org
2024-06-11 17:10 ` 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-114367-4-TxDfUavz03@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).