Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Keven Boell <keven.boell@linux.intel.com>
Cc: Keven Boell <keven.boell@intel.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Introduce linked list for dynamic attributes
Date: Fri, 20 Mar 2015 21:54:00 -0000	[thread overview]
Message-ID: <20150320215415.GC5273@adacore.com> (raw)
In-Reply-To: <55081368.3060302@linux.intel.com>

> 2015-02-23  Keven Boell  <keven.boell@intel.com>
> 
> 	* gdbtypes.c (resolve_dynamic_type_internal): Adapt
> 	data_location usage to linked list.
> 	(resolve_dynamic_type_internal): Adapt data_location usage
> 	to linked list.
> 	(get_dyn_prop): New function.
> 	(add_dyn_prop): New function.
> 	(copy_dynamic_prop_list): New function.
> 	(copy_type_recursive): Add copy of linked list.
> 	(copy_type): Add copy of linked list.
> 	* gdbtypes.h (enum dynamic_prop_node_kind): Kind of the
> 	dynamic attribute in linked list.
> 	(struct dynamic_prop_list): Dynamic list node.
> 	* dwarf2read.c (set_die_type): Add data_location data to
> 	linked list using helper functions.

I sent Keven the instructions on how to get a sourceware account
a while ago now. In the meantime, I've pushed this patch to master
(after having re-tested it on x86_64-linux, just in case).

-- 
Joel


  reply	other threads:[~2015-03-20 21:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  7:37 Keven Boell
2015-03-02 19:50 ` Joel Brobecker
2015-03-03 13:43   ` Keven Boell
2015-03-03 15:55     ` Joel Brobecker
2015-03-04 12:27       ` Keven Boell
2015-03-05 18:13         ` Joel Brobecker
2015-03-10 12:03           ` Keven Boell
2015-03-16 19:55             ` Joel Brobecker
2015-03-17 11:43               ` Keven Boell
2015-03-20 21:54                 ` Joel Brobecker [this message]
2015-03-03 13:43   ` Keven Boell

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=20150320215415.GC5273@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keven.boell@intel.com \
    --cc=keven.boell@linux.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