public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106272] New: clang build: new warning ? Date: Tue, 12 Jul 2022 18:41:52 +0000 [thread overview] Message-ID: <bug-106272-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106272 Bug ID: 106272 Summary: clang build: new warning ? Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Recent gcc builds with clang say this: libcpp/include/line-map.h:1882:12: warning: moving a temporary object prevents copy elision [-Wpessimizing-move] I have little idea what that means, but the line of code is return std::move (label_text (buffer, true)); This new warning appears about 700 times, so it might be important.
next reply other threads:[~2022-07-12 18:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-12 18:41 dcb314 at hotmail dot com [this message] 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 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@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: linkBe 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).