From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 157CE38582B2; Mon, 24 Oct 2022 16:34:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 157CE38582B2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666629285; bh=16QYgN7UphcYCpYilmZcuDecrrgEQAj3GV6blhRAR98=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qsiVY2WcRJMOnEp5LGJ6AqGdhim0RGKdyY3U+1V4h0vzWcFt0dRpbKjyzIFhCzqPu zilTR30Llut38DipYNB6kmuqbSfbj6EFtjo7rCG3LbLzRGKboerTdtexRnrIjYTZoy UNJtDMmC9pywpZhde5QGRqRsZW9zfW6S5F37KV2I= From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107363] Wrong caret location for "redundant move in return statement" and nvo Date: Mon, 24 Oct 2022 16:34:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on assigned_to everconfirmed cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107363 Marek Polacek changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-10-24 Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot= gnu.org Ever confirmed|0 |1 CC| |mpolacek at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED --- Comment #2 from Marek Polacek --- (In reply to Daniel Bertalan from comment #0) > As an aside, it's a bit annoying to have this warning when the moved type > depends on a template parameter in library code. We are forced to either > silence this warning with a #pragma, or use concepts to have a variant of > the release_value method that does not call std::move for const-qualified= T. Understood, I thought I'd fixed cases like that in=20 https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dcommitdiff;h=3D6602a2b2dee16af6e2d= 451c704789356042b5881 Something's not right here. I need to take a closed look. Thanks for reporting the bug.=