public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek 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 00:52:04 +0000 [thread overview]
Message-ID: <bug-106272-4-GOJUMxoKnV@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
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=106276
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #4)
> (In reply to Eric Gallager from comment #3)
> > Note that GCC has its own version of -Wpessimizing-move, too... any idea why
> > clang's version of the flag catches it, but gcc's doesn't?
>
> No, but I'm going to reduce libcpp/line-map.ii to create a testcase and file
> a bug and since it's my warning, maybe even fix it.
Bug 106276.
next prev parent reply other threads:[~2022-07-13 0:52 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 [this message]
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-GOJUMxoKnV@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).