From: "Agovic, Sanimir" <sanimir.agovic@intel.com>
To: 'Tom Tromey' <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 2/2] handle VLA in a struct or union
Date: Mon, 12 May 2014 15:37:00 -0000 [thread overview]
Message-ID: <0377C58828D86C4588AEEC42FC3B85A71D86CADD@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <87y4yaslrv.fsf@fleche.redhat.com>
> Sanimir> As you have pointed out the limitation of vla within arrays,
> Sanimir> this might as well serve as a test case that we deal with it.
>
> I didn't understand this one, sorry...
>
Add a test for the following limitation:
> + if (t != TYPE_FIELD_TYPE (resolved_type, i)
> + && i != vla_field)
> + error (_("Attempt to resolve a variably-sized type which appears "
> + "in the interior of a structure type"));
>
-Sanimir
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
next prev parent reply other threads:[~2014-05-12 15:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 18:47 [PATCH 0/2] " Tom Tromey
2014-05-08 18:47 ` [PATCH 1/2] minor cleanups in is_dynamic_type Tom Tromey
2014-05-08 18:47 ` [PATCH 2/2] handle VLA in a struct or union Tom Tromey
2014-05-08 19:01 ` pinskia
2014-05-08 19:07 ` Tom Tromey
2014-05-08 20:30 ` Philippe Waroquiers
2014-05-08 21:32 ` Tom Tromey
2014-05-08 21:09 ` Joel Brobecker
2014-05-08 21:33 ` Tom Tromey
2014-05-08 22:38 ` Joel Brobecker
2014-05-09 15:57 ` Joel Brobecker
2014-05-21 17:28 ` Tom Tromey
2014-05-21 18:24 ` Joel Brobecker
2014-05-21 22:02 ` Joel Brobecker
2014-05-21 22:28 ` Tom Tromey
2014-06-04 20:27 ` Tom Tromey
2014-05-09 8:05 ` Agovic, Sanimir
2014-05-09 21:08 ` Tom Tromey
2014-05-12 15:37 ` Agovic, Sanimir [this message]
2014-05-12 17:00 ` Tom Tromey
2014-05-13 7:53 ` Agovic, Sanimir
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=0377C58828D86C4588AEEC42FC3B85A71D86CADD@IRSMSX105.ger.corp.intel.com \
--to=sanimir.agovic@intel.com \
--cc=gdb-patches@sourceware.org \
--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