Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Agovic, Sanimir" <sanimir.agovic@intel.com>
To: 'Chris January' <chris.january@allinea.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
	"Boell, Keven"	<keven.boell@intel.com>,
	"Weinmann, Christoph T"	<christoph.t.weinmann@intel.com>
Subject: RE: Variable Length Arrays (VLA) proposal
Date: Fri, 26 Jul 2013 11:44:00 -0000	[thread overview]
Message-ID: <0377C58828D86C4588AEEC42FC3B85A71763D377@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <1372956951.2796.48.camel@gumtree>

> On Thu, 2013-07-04 at 11:49 +0000, Agovic, Sanimir wrote:
> > Afaik gdb does a combination of:
> >
> > const char * exp = [...]
> > struct expression *expr = parse_expression (exp);
> > struct value *val = evaluate_type (expr);
> > [...]
> >
> > for whatis/ptype therefore we should be fine as we have a value in place.
> 
> 1. The value is not passed through to f_print_type.
> 2. evaluate_type evaluates expr with no side effects and no memory reads
> - but for VLA the type depends on the actual value so you do not to
> evaluate with side effects.
>
Chris, thanks for hint. Regarding 2) we may go simply with printing unbound 
dimensions e.g. (: : :). Later we can decide to either relax the no side effects
flag and print the bounds or keep it as-is.

 -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

  reply	other threads:[~2013-07-26 11:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 13:03 Agovic, Sanimir
2013-06-28 15:40 ` Chris January
2013-07-01  1:55   ` Joel Brobecker
2013-07-01  8:01     ` Chris January
2013-07-01 15:32   ` Agovic, Sanimir
2013-07-04  8:18   ` Agovic, Sanimir
2013-07-04  9:13     ` Chris January
2013-07-04 11:49       ` Agovic, Sanimir
2013-07-04 16:55         ` Chris January
2013-07-26 11:44           ` Agovic, Sanimir [this message]
     [not found]     ` <1372928011.2796.13.camel@gumtree>
2013-07-04 10:00       ` Chris January
2013-07-02 13:37 ` Jan Kratochvil
2013-07-02 19:21   ` Jan Kratochvil
2013-07-02 22:22     ` Joel Brobecker
2013-07-04 12:32   ` Keven Boell
2013-08-04 19:33     ` Jan Kratochvil
2013-08-07  5:25       ` Keven Boell
2013-08-04 19:02 ` 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=0377C58828D86C4588AEEC42FC3B85A71763D377@IRSMSX105.ger.corp.intel.com \
    --to=sanimir.agovic@intel.com \
    --cc=chris.january@allinea.com \
    --cc=christoph.t.weinmann@intel.com \
    --cc=gdb@sourceware.org \
    --cc=keven.boell@intel.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