From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id A48E23885512; Wed, 13 Jul 2022 18:23:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A48E23885512
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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: 
Message-ID: <bug-106272-4-CTjbAAM1GT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106272-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106272-4@http.gcc.gnu.org/bugzilla/>
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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2022 18:23:54 -0000

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

--- 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:
=20=20=20
<https://developers.redhat.com/blog/2019/04/12/understanding-when-not-to-st=
dmove-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 f=
iled
    PR106276 to track that.

            PR preprocessor/106272

    libcpp/ChangeLog:

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