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++/100823] Special member functions of common_iterator should be conditionally trivial
Date: Wed, 20 Jul 2022 22:59:20 +0000	[thread overview]
Message-ID: <bug-100823-4-Wql0L25ujS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100823-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:87a9bfe86d8a87d09de5d60e430d14bfa6c816f0

commit r13-1771-g87a9bfe86d8a87d09de5d60e430d14bfa6c816f0
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Jul 20 16:51:44 2022 +0100

    libstdc++: Fix std::common_iterator triviality [PR100823]

    This fixes the remaining problem reported in the PR, that the special
    members should be trivial.  This can be done by constraining the
    non-trivial versions and adding defaulted overloads that will be used
    when the union members are trivial.

    Making these members trivial alters the argument passing ABI and so
    isn't suitable for backporting to release branches.

    libstdc++-v3/ChangeLog:

            PR libstdc++/100823
            * include/bits/stl_iterator.h (common_iterator): Define
            destructor, copy constructor and move constructor as trivial
            when the underlying types allow.
            * testsuite/24_iterators/common_iterator/100823.cc: Check
            triviality of special members.

  parent reply	other threads:[~2022-07-20 22:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29  5:47 [Bug libstdc++/100823] New: " rs2740 at gmail dot com
2021-06-17 12:30 ` [Bug libstdc++/100823] " redi at gcc dot gnu.org
2021-06-29 19:14 ` redi at gcc dot gnu.org
2022-07-20 22:59 ` cvs-commit at gcc dot gnu.org
2022-07-20 22:59 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-20 23:01 ` redi at gcc dot gnu.org
2022-07-21 11:17 ` cvs-commit at gcc dot gnu.org
2022-07-22  7:08 ` cvs-commit at gcc dot gnu.org
2022-07-22  7:10 ` redi at gcc dot gnu.org
2023-04-27 23:04 ` cvs-commit at gcc dot gnu.org
2023-04-27 23:06 ` 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-100823-4-Wql0L25ujS@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).