public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6024: GCC fails to diagnose mismatch of enum types in prototype/function Date: Thu, 21 Mar 2002 03:36:00 -0000 [thread overview] Message-ID: <20020321113603.17157.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6024; it has been noted by GNATS. From: Richard Earnshaw <rearnsha@arm.com> To: "Joseph S. Myers" <jsm28@cam.ac.uk> Cc: rearnsha@arm.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: c/6024: GCC fails to diagnose mismatch of enum types in prototype/function Date: Thu, 21 Mar 2002 11:30:58 +0000 > The types are compatible, which means these declarations are OK. (Unless > you use -fshort-enums, in which case the type in the prototype disagrees > with the promoted type from the non-prototype definition.) I *might* accept that argument if -Wall gave a diagnostic message for this. However, I don't see why this case is any different from struct s1 {int a, int b}; struct s2 {int c, int d}; void f(struct s1 *); void f(x) struct s2 *x; { return; } s1 and s2 are 'compatible'; but they aren't the same. Where in the standard does it say that enum types are 'weak' like this?
next reply other threads:[~2002-03-21 11:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-21 3:36 Richard Earnshaw [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-07 2:35 bangerth 2002-03-21 3:56 Joseph S. Myers 2002-03-21 3:26 Joseph S. Myers 2002-03-21 3:06 rearnsha
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=20020321113603.17157.qmail@sources.redhat.com \ --to=rearnsha@arm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).