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++/96766] std::swap(std::variant, std::variant) triggers undefined behavior sanitizer
Date: Mon, 24 Aug 2020 15:15:05 +0000	[thread overview]
Message-ID: <bug-96766-4-4QGn1A8JaG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96766-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:074436cf8cdd2a9ce75cadd36deb8301f00e55b9

commit r11-2822-g074436cf8cdd2a9ce75cadd36deb8301f00e55b9
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Aug 24 16:10:07 2020 +0100

    libstdc++: Make variant_npos conversions explicit [PR 96766]

    libstdc++-v3/ChangeLog:

            PR libstdc++/96766
            * include/std/variant (_Variant_storage): Replace implicit
            conversions from size_t to __index_type with explicit casts.

  parent reply	other threads:[~2020-08-24 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 12:25 [Bug libstdc++/96766] New: " kndevl at outlook dot com
2020-08-24 12:33 ` [Bug libstdc++/96766] " kndevl at outlook dot com
2020-08-24 12:43 ` redi at gcc dot gnu.org
2020-08-24 12:49 ` redi at gcc dot gnu.org
2020-08-24 15:15 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-26 12:54 ` cvs-commit at gcc dot gnu.org
2020-08-26 12:58 ` cvs-commit at gcc dot gnu.org
2020-08-26 13:00 ` redi at gcc dot gnu.org
2022-07-19 13:56 ` cvs-commit at gcc dot gnu.org
2022-07-21 11:16 ` 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-96766-4-4QGn1A8JaG@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).