public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
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:56:00 -0000	[thread overview]
Message-ID: <20020321115606.17369.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/6024; it has been noted by GNATS.

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <Richard.Earnshaw@arm.com>
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:51:07 +0000 (GMT)

 On Thu, 21 Mar 2002, Richard Earnshaw wrote:
 
 > struct s1 {int a, int b};
 > struct s2 {int c, int d};
 
 > 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?
 
 s1 and s2 aren't compatible.  Compatibility is defined in 6.2.7#1,
 augmented by 6.7.2.2#4 (which specifies that enumerated types are
 compatible with char or a signed or unsigned integer type) and some other
 clauses.  There are rules about when structure types in different
 translation units are compatible, but nothing that would make s1 and s2
 compatible in any case.  (However, I can't see anything that says that two
 enumerated types compatible with "int" (say) are compatible with each
 other either, so it isn't clear what's intended here.)
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2002-03-21 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21  3:56 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07  2:35 bangerth
2002-03-21  3:36 Richard Earnshaw
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=20020321115606.17369.qmail@sources.redhat.com \
    --to=jsm28@cam.ac.uk \
    --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: 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).