From: Joseph Myers <joseph@codesourcery.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add warning options -W[no-]compare-distinct-pointer-types
Date: Mon, 8 Aug 2022 18:14:17 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2208081812390.1210622@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87mtciu23z.fsf@oracle.com>
On Fri, 5 Aug 2022, Jose E. Marchesi via Gcc-patches wrote:
> +Wcompare-distinct-pointer-types
> +C C++ Var(warn_compare_distinct_pointer_types) Warning Init(1)
> +Warn if pointers of distinct types are compared without a cast.
There's no implementation for C++ in this patch, so the option shouldn't
be supported for C++ in c.opt. However, C options are normally supported
for Objective-C; unless you have a specific reason why Objective-C support
for this option would be a bad idea, "C ObjC" would be appropriate for the
languages.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-08-08 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 15:44 Jose E. Marchesi
2022-08-08 18:14 ` Joseph Myers [this message]
2022-08-18 13:01 ` [PATCH V2] " Jose E. Marchesi
2022-08-18 15:34 ` Joseph Myers
2022-08-26 15:45 ` Jose E. Marchesi
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=alpine.DEB.2.22.394.2208081812390.1210622@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jose.marchesi@oracle.com \
/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).