Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Eliminate char buf[MAX_REGISTER_RAW_SIZE]
Date: Sat, 01 Feb 2003 17:33:00 -0000	[thread overview]
Message-ID: <200302011733.h11HXne21013@duracef.shout.net> (raw)

Michael Snyder writes:

> Some compilers will not allow a function call in an auto initializer.

I think you are thinking of

  static int i = foo ();  /* not legal in any C standard that I know */

Rather than

  auto int i = foo ();  /* been legal since K&R C */

Static and global initializers have to be resolved by link time so they
have to be constants or nearly constant (address expressions like
'&array' or '&function).  Auto initializers can be any expression
including function calls.  It's been that way since K&R C.

It would take a really deficient compiler to screw that up.  I
acknowledge that there is no limit to how messed up a vendor C compiler
can actually be.  So I took a quick look at utils.c (at random) to see
if gdb uses this construct anywhere else.  And it does:

  /* gdb 5.2.1 utils.c */
  struct cleanup *
  make_cleanup_close (int fd)
  {
    int *saved_fd = xmalloc (sizeof (fd));
    ...
  }

  void
  quit (void)
  {
    struct serial *gdb_stdout_serial = serial_fdopen (1);
    ...
  }

So we are safe on this point.

Michael C


             reply	other threads:[~2003-02-01 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-01 17:33 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-31 22:58 Andrew Cagney
2003-01-31 23:20 ` Andreas Schwab
2003-01-31 23:26   ` Andrew Cagney
2003-02-01  1:36 ` Michael Snyder
2003-02-01  6:17   ` Andrew Cagney
2003-02-01  6:13 ` Joel Brobecker
2003-02-01  6:40   ` Andrew Cagney
2003-02-02  5:36 ` Andrew Cagney

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=200302011733.h11HXne21013@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.com \
    /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