public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104559] New: vector<bool> v; v.insert(v.begin()); compiles, but it shouldn't
Date: Tue, 15 Feb 2022 22:31:11 +0000	[thread overview]
Message-ID: <bug-104559-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104559
           Summary: vector<bool> v; v.insert(v.begin()); compiles, but it
                    shouldn't
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: arthur.j.odwyer at gmail dot com
  Target Milestone: ---

// https://godbolt.org/z/3efs3aY67
#include <vector>
int main() {
    std::vector<bool> v;
    v.insert(v.begin());  // libstdc++ accepts!
}

Somehow libstdc++ believes that `vector<bool>::insert(_Bit_const_reference)`
should work. (I bet it inserts "false" at the given position, but I haven't
checked.)

             reply	other threads:[~2022-02-15 22:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 22:31 arthur.j.odwyer at gmail dot com [this message]
2022-02-15 22:50 ` [Bug libstdc++/104559] " pinskia at gcc dot gnu.org
2022-02-16  9:32 ` redi at gcc dot gnu.org
2022-02-16 10:01 ` de34 at live dot cn
2022-02-17 10:48 ` redi at gcc dot gnu.org
2022-02-17 23:45 ` cvs-commit at gcc dot gnu.org
2022-02-17 23:46 ` redi at gcc dot gnu.org
2022-02-17 23:46 ` 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-104559-4@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).