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 c++/107363] Wrong caret location for "redundant move in return statement" and nvo
Date: Wed, 09 Nov 2022 02:37:31 +0000	[thread overview]
Message-ID: <bug-107363-4-gCgjGm9XkH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107363-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:b305793b985f4d3e0032b04d446b8baabcb3e8b7

commit r13-3822-gb305793b985f4d3e0032b04d446b8baabcb3e8b7
Author: Marek Polacek <polacek@redhat.com>
Date:   Fri Oct 28 13:39:40 2022 -0400

    c++: Tweaks for -Wredundant-move [PR107363]

    Two things here:

    1) when we're pointing out that std::move on a constant object is
       redundant, don't say "in return statement" when we aren't in a
       return statement;
    2) suppress the warning when the std::move call was dependent, because
       removing the std::move may not be correct for a different
       instantiation of the original template.

            PR c++/107363

    gcc/cp/ChangeLog:

            * semantics.cc (finish_call_expr): Suppress OPT_Wpessimizing_move.
            * typeck.cc (maybe_warn_pessimizing_move): Check
warn_redundant_move
            and warning_suppressed_p.  Adjust a message depending on return_p.
            (check_return_expr): Don't suppress OPT_Wpessimizing_move here.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/Wredundant-move13.C: New test.

  parent reply	other threads:[~2022-11-09  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23  9:43 [Bug c++/107363] New: Wrong caret location for "redundant move in return statement" dani at danielbertalan dot dev
2022-10-23 15:52 ` [Bug c++/107363] Wrong caret location for "redundant move in return statement" and nvo pinskia at gcc dot gnu.org
2022-10-24 16:34 ` mpolacek at gcc dot gnu.org
2022-11-09  2:37 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-09  2:52 ` mpolacek at gcc dot gnu.org
2022-11-28 22:17 ` pinskia 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-107363-4-gCgjGm9XkH@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).