Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>
Subject: Re: [RFC] rl78: vtables are code addresses
Date: Tue, 11 Feb 2014 16:38:00 -0000	[thread overview]
Message-ID: <20140211093820.23de6ad4@redhat.com> (raw)
In-Reply-To: <52F9FE9D.6050603@redhat.com>

On Tue, 11 Feb 2014 10:42:37 +0000
Pedro Alves <palves@redhat.com> wrote:

> Thus, wouldn't it be a little better to mark the baked in struct
> type as code to begin with?
> 
> ---
>  gdb/gnu-v3-abi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdb/gnu-v3-abi.c b/gdb/gnu-v3-abi.c
> index a08dc36..ceccbe5 100644
> --- a/gdb/gnu-v3-abi.c
> +++ b/gdb/gnu-v3-abi.c
> @@ -171,7 +171,7 @@ build_gdb_vtable_type (struct gdbarch *arch)
>    TYPE_TAG_NAME (t) = "gdb_gnu_v3_abi_vtable";
>    INIT_CPLUS_SPECIFIC (t);
> 
> -  return t;
> +  return make_type_with_address_space (t, TYPE_INSTANCE_FLAG_CODE_SPACE);
>  }
> 
> 
> I believe this makes no difference for archs with flat address space.
> (testing on x86-64 GNU/Linux shows no changes).

Very nice.  I've tested your patch and find that it produces
results identical to what I was getting with my patch.  Please
check it in...

(Or, if you'd prefer that I check it in, please let me know.)

Thanks!

Kevin


  reply	other threads:[~2014-02-11 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  6:44 Kevin Buettner
2014-02-11  9:30 ` Joel Brobecker
2014-02-11 10:42 ` Pedro Alves
2014-02-11 16:38   ` Kevin Buettner [this message]
2014-02-12 13:32     ` Pedro Alves
2014-02-12 19:42       ` Kevin Buettner

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=20140211093820.23de6ad4@redhat.com \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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