Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Maxim Grigoriev <maxim@tensilica.com>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	  Ulrich Weigand <uweigand@de.ibm.com>,
	 Eli Zaretskii <eliz@gnu.org>,
	Joel Brobecker <brobecker@adacore.com>,
	  Jim Blandy <jimb@codesourcery.com>,
	  rearnsha@arm.com, Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [rfc] [00/16] Get rid of current gdbarch
Date: Mon, 08 Oct 2007 17:53:00 -0000	[thread overview]
Message-ID: <470A6EE5.4030104@hq.tensilica.com> (raw)
In-Reply-To: <4709E786.1070502@de.ibm.com>

Hello, Markus,

I think you missed xtenda-tdep.c.
First time, you asked for an approval but never checked the patch in.

What do you want me to do : to wait until you update it and then test 
it, or just go ahead and do it by myself ?

-- Maxim


Markus Deuling wrote:
> Hi,
>
> a while ago I sent a first patch set to get rid of current_gdbarch. I 
> now added some patches and deferred some other and reworked the 
> ChangeLog entries due to feedback from you. Now that 6.7 branch was 
> created this is a reworked patch set for current head.
>
> This patch set is another step in the direction of per-frame 
> architecture. This set of 16 patches replaces (trivial to replace 
> occurences of) current_gdbarch by appropriate methods like 
> get_frame_arch or get_regcache_arch etc.
>
> Currently get_frame_arch just returns current_gdbarch but this will be 
> replaced by later patches.
>
> I tested this patch set on x86 native and remote by compiling and 
> running the testsuite. I also did a gdb_mbuild with all
> targets to make sure it compiles.
>
> Some later patches will be non-trivial and hard for me to test due to 
> lack of those machines. It would be great if some of you could test 
> patches for different archs like mips, arm, etc. but this will still 
> take a while.
>
> This patch set replaces some of the current_gdbarch's in following files:
>
> * aix-thread.c
> * arm-tdep.c
> * alpha-{linux-nat,nat,tdep}.c
> * findvar.c
> * amd64-{nat,tdep}.c
> * i386-tdep.c
> * sh[64]-tdep.c
> * remote.c
> * irix5-nat.c
> * regcache.c
> * m68k{linux-nat, linux-tdep, -tdep}.c
> * dwarf2{loc, -frame}.c
> * cris-tdep.c
> * hppa-{hpux-nat, hpux-tdep, linux-nat, tdep}.c
>
> Is this ok?
>
>
>


  parent reply	other threads:[~2007-10-08 17:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08  8:18 Markus Deuling
2007-10-08 13:03 ` Ulrich Weigand
2007-10-08 13:22   ` Markus Deuling
2007-10-08 13:35   ` Daniel Jacobowitz
2007-10-08 14:01     ` Ulrich Weigand
2007-10-08 14:10       ` Daniel Jacobowitz
2007-10-09 20:03         ` Ulrich Weigand
2007-10-09 21:39           ` Daniel Jacobowitz
2007-10-10 11:54             ` Mark Kettenis
2007-10-10 12:01               ` Daniel Jacobowitz
2007-10-08 13:16 ` Joel Brobecker
2007-10-09  7:02   ` Markus Deuling
2007-10-08 17:53 ` Maxim Grigoriev [this message]
2007-10-09  5:10   ` Markus Deuling

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=470A6EE5.4030104@hq.tensilica.com \
    --to=maxim@tensilica.com \
    --cc=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=rearnsha@arm.com \
    --cc=uweigand@de.ibm.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