Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Test struct0
Date: Wed, 04 Feb 2004 00:46:00 -0000	[thread overview]
Message-ID: <20040204004620.GA9431@nevyn.them.org> (raw)
In-Reply-To: <40203797.8010607@gnu.org>

On Tue, Feb 03, 2004 at 07:06:47PM -0500, Andrew Cagney wrote:
> Hello,
> 
> This adds a test for:
> 
> 	struct foo0 { };
> 
> to the structs.exp testcase (I'm assuming that this is legal ISO-C), it 

Nope.

      struct-or-union-specifier:
           struct-or-union identifier-opt { struct-declaration-list }
           struct-or-union identifier

      struct-or-union:
           struct
           union

      struct-declaration-list:
           struct-declaration
           struct-declaration-list struct-declaration

      struct-declaration:
           specifier-qualifier-list struct-declarator-list ;

So there must be a minimum of one declarator and trailing semicolon
inside the braces.  GCC will warn about this if you ask it to - it's
probably -ansi, or -std=c89 -ansi -pedantic.

While it's not legal C, I believe that it is legal C++.

> passes on PPC with stabs with:
> 
> >(gdb) PASS: gdb.base/structs.exp: ptype foo1; structs-tc
> >p/c fun0()
> >$1 = {<No data fields>}
> 
> Tt was intended for completness, however with a dwarf2 compiler:
> 
> amd64$ gcc --version
> gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
> 
> >(gdb) PASS: gdb.base/structs.exp: ptype foo1; structs-tc
> >p/c fun0()
> >$1 = <incomplete type>
> 
> I guess I should file a bug report and kfail it?

If you want to add the test anyway and run it where it compiles, then
yeah.  I assume this runs afoul of the handling for declarations/opaque
types.  It would be nice to support it even if it's a GNU extension.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-04  0:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04  0:06 Andrew Cagney
2004-02-04  0:46 ` Daniel Jacobowitz [this message]
2004-02-04  1:34   ` Joel Brobecker
2004-02-04 15:52   ` Andrew Cagney
2004-02-04 15:59     ` Daniel Jacobowitz
2004-02-10 21:07 ` 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=20040204004620.GA9431@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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