From: Joel Brobecker <brobecker@adacore.com>
To: Pierre-Marie de Rodat <derodat@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Do not consider reference types as dynamic
Date: Fri, 03 Apr 2015 12:47:00 -0000 [thread overview]
Message-ID: <20150403124724.GC4704@adacore.com> (raw)
In-Reply-To: <551E5309.7090509@adacore.com>
> >From f3fd1a7e81fad7a0b8e4f483f79b2470a3cf1499 Mon Sep 17 00:00:00 2001
> From: Pierre-Marie de Rodat <derodat@adacore.com>
> Date: Fri, 3 Apr 2015 10:40:52 +0200
> Subject: [PATCH] Do not consider reference types as dynamic
>
> Even when referenced types are dynamic, the corresponding referencing
> type should not be considered as dynamic: it's only a pointer. This
> prevents reference type for values not in memory to be resolved.
>
> gdb/ChangeLog:
> 2015-04-03 Pierre-Marie de Rodat <derodat@adacore.com>
>
> * gdbtypes.c (is_dynamic_type_internal): Remove special handling
> of TYPE_CODE_REF types so that they are not considered as
> dynamic depending on the referenced type.
> (resolve_dynamic_type_internal): Likewise.
>
> gdb/testsuite/ChangeLog:
> 2015-04-03 Pierre-Marie de Rodat <derodat@adacore.com>
>
> * gdb.ada/funcall_ref.exp: New file.
> * gdb.ada/funcall_ref/foo.adb: New file.
This is OK, thank you, Pierre-Marie.
Note that the parameter "top_level" is no longer useful after
this patch is applied, which is actually quite a nice side-effect
of this patch. I hum'ed and ah'ed about whether to ask that it be
removed as part of this patch, but in the end, I decided that this patch
was fine without the cleanup, as "top_level" is used a several places,
and I felt that cleaning it up here would dilute a bit the essence of
this patch. So, I think we can clean it up separately.
> diff --git a/gdb/gdbtypes.c b/gdb/gdbtypes.c
> index 217ec70..6fb2e9a 100644
> --- a/gdb/gdbtypes.c
> +++ b/gdb/gdbtypes.c
> @@ -1752,10 +1752,6 @@ is_dynamic_type_internal (struct type *type, int top_level)
Thank you,
--
Joel
next prev parent reply other threads:[~2015-04-03 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 11:57 Pierre-Marie de Rodat
2015-03-23 13:36 ` Joel Brobecker
2015-04-01 8:52 ` Pierre-Marie de Rodat
2015-04-03 8:45 ` Pierre-Marie de Rodat
2015-04-03 12:47 ` Joel Brobecker [this message]
2015-04-03 13:02 ` Pierre-Marie de Rodat
2015-04-03 13:12 ` Joel Brobecker
2015-04-03 13:25 ` Pierre-Marie de Rodat
2015-04-17 10:47 ` Yao Qi
2015-04-17 11:20 ` Pierre-Marie de Rodat
2015-04-17 15:07 ` Pierre-Marie de Rodat
2015-04-17 15:29 ` Joel Brobecker
2015-04-20 14:27 ` Pierre-Marie de Rodat
2015-04-24 14:22 ` Pierre-Marie de Rodat
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=20150403124724.GC4704@adacore.com \
--to=brobecker@adacore.com \
--cc=derodat@adacore.com \
--cc=gdb-patches@sourceware.org \
/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