public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/22249] GCC does not reject an incompatible type declaration
Date: Wed, 02 Mar 2022 02:31:15 +0000 [thread overview]
Message-ID: <bug-22249-4-ug3PeHk3WS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-22249-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=22249
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Uecker from comment #2)
> This is diagnosed in GCC 11.
>
> https://godbolt.org/z/GcE19jqbK
...as a warning, but I think the original reporter wanted it to be an error?
(or at least as a pedwarn instead of a regular warning)
next prev parent reply other threads:[~2022-03-02 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22249-4@http.gcc.gnu.org/bugzilla/>
2021-08-14 20:09 ` muecker at gwdg dot de
2022-03-02 2:31 ` egallager at gcc dot gnu.org [this message]
2005-06-30 13:20 [Bug c/22249] New: " neil at gcc dot gnu dot org
2005-06-30 13:33 ` [Bug c/22249] " pinskia at gcc dot gnu dot 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-22249-4-ug3PeHk3WS@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).