[rfc] [00/12] Get rid of current_gdbarch

[rfc] [00/12] Get rid of current_gdbarch

[Markus Deuling]

Hi,

this and the next patch sets are another step in the direction of per-frame architecture. To achieve that
goal GDB needs to get rid of the global variable current_gdbarch. This set of 12 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), ppc and ppc64 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
* frame.c
* i386-tdep.c
* mips-tdep.c
* ppc-linux-nat.c
* rs6000-tdep.c
* sh[64]-tdep.c
* xtensa-tdep.c
* remote.c

Is this ok?

-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com

Re: [rfc] [00/12] Get rid of current_gdbarch

[Jim Blandy]

Markus Deuling <deuling@de.ibm.com> writes:
> Is this ok?

This is wonderful.  Thanks for undertaking this work, which must not
have been too exciting.

With all these patches applied, how many references to current_gdbarch
remain?

Re: [rfc] [00/12] Get rid of current_gdbarch

[Joel Brobecker]

> 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.

I can help with some of the testing, as usual. But I'm a bit nervous,
and I think it would be nice to branch off gdb-6.7 before applying
these particular trickier changes. The only thing that is holding me
up is the change of licensing in the source headers. I was kinda hoping
that the well known "someone" would take care of it while I'm on holiday,
but I might have to jump in and help with the effort. I really want to
see gdb-6.7 out soon!

In the meantime, I propose to hold the tricky patches until the
gdb-6.7 branch is created. Would that be ok?

-- 
Joel

Re: [rfc] [00/12] Get rid of current_gdbarch

[Markus Deuling]

Joel Brobecker schrieb:
> I can help with some of the testing, as usual. But I'm a bit nervous,
This would be great, thank you!

> and I think it would be nice to branch off gdb-6.7 before applying
> these particular trickier changes. The only thing that is holding me
> up is the change of licensing in the source headers. I was kinda hoping
> that the well known "someone" would take care of it while I'm on holiday,
> but I might have to jump in and help with the effort. I really want to
> see gdb-6.7 out soon!
> 
> In the meantime, I propose to hold the tricky patches until the
> gdb-6.7 branch is created. Would that be ok?

Sure, I'm fine with that. I have to redo the ChangeLog of the patch set and 
will then repost it. We'll wait until 6.7 for comitting these ones.



-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com