Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.6 released!
Date: Mon, 29 Apr 2013 14:37:00 -0000	[thread overview]
Message-ID: <20130429043214.GV3525@adacore.com> (raw)
In-Reply-To: <83ip36sjxd.fsf@gnu.org>

> > I am wondering why we are not seeing this on other platforms...
> 
> Probably because I was using a _really_ old compiler (3.4.2) on the
> machine where I saw this.

This would suggest that I misunderstood the C standard regarding
enum types. I thought that the size of a C enum was determined
by the number of enumerators (ie just large enough to fit), which
would mean that the compiler would need the full enum definition
before being able to determine how to pass that enum in a function
call. But the reference draft I have says:

    | Each enumerated type shall be compatible with an integer type. The
    | choice of type is implementation-defined,97) but shall be capable of
    | representing the values of all the members of the enumeration.

I am still a little fuzzy on what "compatible" means in terms of
constraints for the enum type. But perhaps the old compiler's
warning is overzealous; and if that's the case, I am not sure of
the value of avoiding erroneous warnings from really old compilers.

-- 
Joel


  reply	other threads:[~2013-04-29  4:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <announce.20130426140741.GA13837@adacore.com>
     [not found] ` <83k3nptk18.fsf@gnu.org>
2013-04-28 22:59   ` Eli Zaretskii
2013-04-29  9:53     ` Joel Brobecker
2013-04-29 12:48       ` Eli Zaretskii
2013-04-29 14:37         ` Joel Brobecker [this message]
2013-04-29 15:24           ` Andreas Schwab
2013-05-05 19:44       ` Jan Kratochvil
2013-05-06 10:32         ` Joel Brobecker
2013-05-06 16:19           ` Eli Zaretskii
2013-05-06 18:19             ` Tom Tromey

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=20130429043214.GV3525@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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