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 preprocessor/106272] clang build: new warning ?
Date: Wed, 13 Jul 2022 18:23:54 +0000	[thread overview]
Message-ID: <bug-106272-4-CTjbAAM1GT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106272-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:86a15b266a7284f3aa1b12494a475f31416b981d

commit r13-1689-g86a15b266a7284f3aa1b12494a475f31416b981d
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Jul 12 20:18:56 2022 -0400

    libcpp: Avoid pessimizing std::move [PR106272]

    std::move in a return statement can prevent the NRVO:
   
<https://developers.redhat.com/blog/2019/04/12/understanding-when-not-to-stdmove-in-c>

    PR106272 reports that we have two such cases in class label_text's
    member functions.  We have -Wpessimizing-move that's supposed to detect
    problematic std::move uses, but in this case it didn't trigger.  I've filed
    PR106276 to track that.

            PR preprocessor/106272

    libcpp/ChangeLog:

            * include/line-map.h (class label_text): Don't std::move in a
return
            statement.

  parent reply	other threads:[~2022-07-13 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 18:41 [Bug c/106272] New: " dcb314 at hotmail dot com
2022-07-12 19:02 ` [Bug preprocessor/106272] " redi at gcc dot gnu.org
2022-07-12 19:35 ` dcb314 at hotmail dot com
2022-07-12 20:26 ` egallager at gcc dot gnu.org
2022-07-13  0:09 ` mpolacek at gcc dot gnu.org
2022-07-13  0:17 ` mpolacek at gcc dot gnu.org
2022-07-13  0:52 ` mpolacek at gcc dot gnu.org
2022-07-13 18:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-13 18:25 ` mpolacek at gcc dot gnu.org
2022-07-13 19:11 ` dmalcolm 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-106272-4-CTjbAAM1GT@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).