This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] [17/17] Get rid of current_gdbarch in go32-nat.c
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Markus Deuling <deuling at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org, uweigand at de dot ibm dot com
- Date: Fri, 12 Oct 2007 10:08:34 +0200
- Subject: Re: [rfc] [17/17] Get rid of current_gdbarch in go32-nat.c
- References: <470DE4C1.9070509@de.ibm.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 11 Oct 2007 10:54:25 +0200
> From: Markus Deuling <deuling@de.ibm.com>
> CC: Ulrich Weigand <uweigand@de.ibm.com>
>
> this patch gets rid of some of the current_gdbarch's in go32-nat.c
> Is this ok to commit?
>
> ChangeLog:
>
>
> * go32-nat.c (fetch_register, go32_fetch_registers, store_register)
> (go32_store_registers): Use get_regcache_arch to get at the current
> architecture by regcache.
Sorry for asking this so late, but could you please explain the
reason(s) why these changes are a good idea, i.e. what potential
problem(s) are they trying to solve? If I tell you that the go32
(a.k.a. DJGPP) native build of GDB supports only a single
architecture, would those reason(s) still hold?