public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110807] [13/14 Regression] Copy list initialisation of a vector<bool> raises a warning with -O2 Date: Wed, 26 Jul 2023 13:34:27 +0000 [thread overview] Message-ID: <bug-110807-4-wNTbeSPwmg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110807-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- A similar change in vector<bool>::_M_insert_range fixes this one though.
next prev parent reply other threads:[~2023-07-26 13:34 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-25 18:26 [Bug c++/110807] New: " twic at urchin dot earth.li 2023-07-26 6:30 ` [Bug tree-optimization/110807] " pinskia at gcc dot gnu.org 2023-07-26 6:32 ` [Bug tree-optimization/110807] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-07-26 7:43 ` [Bug libstdc++/110807] " rguenth at gcc dot gnu.org 2023-07-26 12:04 ` redi at gcc dot gnu.org 2023-07-26 13:34 ` redi at gcc dot gnu.org [this message] 2023-07-26 13:34 ` redi at gcc dot gnu.org 2023-07-26 16:02 ` cvs-commit at gcc dot gnu.org 2023-07-26 16:04 ` [Bug libstdc++/110807] [13 " redi at gcc dot gnu.org 2023-07-26 18:11 ` cvs-commit at gcc dot gnu.org 2023-07-28 10:13 ` redi at gcc dot gnu.org 2023-07-28 17:32 ` cvs-commit at gcc dot gnu.org 2023-07-28 19:00 ` redi at gcc dot gnu.org 2023-11-06 12:20 ` aoliva at gcc dot gnu.org 2023-11-06 12:38 ` redi at gcc dot gnu.org 2023-11-09 3:30 ` cvs-commit at gcc dot gnu.org 2024-02-09 8:46 ` cvs-commit 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-110807-4-wNTbeSPwmg@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: linkBe 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).