Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: tromey@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [no-commit-intention] Naive unnamed fields for main_type  [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes]
Date: Sun, 12 Feb 2012 19:23:00 -0000	[thread overview]
Message-ID: <20120212192313.GA25793@host2.jankratochvil.net> (raw)
In-Reply-To: <201202121019.q1CAJoQw025308@glazunov.sibelius.xs4all.nl>

On Sun, 12 Feb 2012 11:19:50 +0100, Mark Kettenis wrote:
> On OpenBSD we still have some platforms stuck with GCC 2.95.

And does it support unnamed fields?

echo 'struct { int a; struct { int b; }; } s;'|gcc -c -x c - -Wall 

At least gcc-2.96-116.7.2.i386 does.


> already includes quite a bit of C99 functionality, but some bits are
> missing.

So maybe unnamed fields are OK for GDB?


Thanks,
Jan


  reply	other threads:[~2012-02-12 19:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  9:28 [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Jan Kratochvil
2012-02-09  9:32 ` [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes] Jan Kratochvil
2012-02-09 15:16   ` Joel Brobecker
2012-02-09 15:37     ` Jan Kratochvil
2012-02-09 18:56       ` Eli Zaretskii
2012-02-10 18:05       ` Tom Tromey
2012-02-10 19:01         ` Jan Kratochvil
2012-02-10 19:22           ` Tom Tromey
2012-02-10 19:29             ` Jan Kratochvil
2012-02-12 10:20             ` Mark Kettenis
2012-02-12 19:23               ` Jan Kratochvil [this message]
2012-02-09 19:07     ` Alfred M. Szmidt
2012-02-09 19:23     ` Stan Shebs
2012-02-10 18:07       ` Tom Tromey
2012-02-09 15:12 ` [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Joel Brobecker
2012-02-09 15:15   ` [commit] " Jan Kratochvil

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=20120212192313.GA25793@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=tromey@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