public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/109835] -Wincompatible-function-pointer-types as a subset of -Wincompatible-pointer-types?
Date: Fri, 22 Mar 2024 14:12:03 +0000	[thread overview]
Message-ID: <bug-109835-4-zkUYEeBcY6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109835-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Sam James <sjames at gcc dot gnu.org> ---
FWIW, after doing more of this work, I've decided I don't really care that much
about this one.

I still think FP mismatches are often worse, but there's enough junk pointer
type mismatches that I'm not sure we should provide this (it's not like one
case is OK and the other is way less scary or something).

  parent reply	other threads:[~2024-03-22 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 16:18 [Bug c/109835] New: " sjames at gcc dot gnu.org
2023-05-12 16:49 ` [Bug c/109835] " fw at gcc dot gnu.org
2023-05-12 21:13 ` sjames at gcc dot gnu.org
2023-05-13 15:05 ` egallager at gcc dot gnu.org
2023-05-13 22:56 ` sjames at gcc dot gnu.org
2024-03-22 14:12 ` sjames at gcc dot gnu.org [this message]
2024-03-22 22:43 ` egallager 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-109835-4-zkUYEeBcY6@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).