Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING][PATCH][exp] Interpret size of vla with unknown size as <optimized out>
Date: Fri, 27 Jul 2018 15:18:00 -0000	[thread overview]
Message-ID: <871sbo7ln9.fsf@tromey.com> (raw)
In-Reply-To: <1822d1ff-9cc6-f4ec-d5fd-e223f0af6265@suse.de> (Tom de Vries's	message of "Wed, 25 Jul 2018 16:22:45 +0200")

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> [gdb/exp] Interpret size of vla with unknown size as <optimized out>

Tom> 2018-07-06  Tom de Vries  <tdevries@suse.de>

Tom> 	* eval.c (evaluate_subexp_for_sizeof): Interpret size of dynamic type
Tom> 	with undefined upper bound as <optimized out>.

Tom> 	* gdb.base/vla-optimized-out-o3.c: New test.
Tom> 	* gdb.base/vla-optimized-out-o3.exp: New file.

Thanks.  This seems like a reasonable approach to me.
Please check it in.

Tom


      reply	other threads:[~2018-07-27 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 13:27 [PATCH][exp] " Tom de Vries
2018-07-25 14:22 ` [PING][PATCH][exp] " Tom de Vries
2018-07-27 15:18   ` Tom Tromey [this message]

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=871sbo7ln9.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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