Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	        Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [rfc]  Get rid of current_gdbarch in amd64
Date: Tue, 15 Jan 2008 04:45:00 -0000	[thread overview]
Message-ID: <478C39D3.9070403@de.ibm.com> (raw)
In-Reply-To: <20080112094319.GC9143@adacore.com>

Joel Brobecker schrieb:
>> I dont have access to an AMD64 machine. Maybe someone from this list has 
>> and could do a testrun
>> with this patch to see if there are regressions? Thanks a lot.
> [...]
>> ChangeLog:
>>
>> 	* amd64-nat.h (amd64_native_gregset_supplies_p): Add gdbarch as 
>> 	parameter.
>> 	* amd64-nat.c (amd64_native_gregset_supplies_p): Likewise.
>>
>> 	(amd64_native_gregset_reg_offset): Add gdbarch as parameter. Replace
>> 	current_gdbarch by gdbarch. Update caller.
>>
>> 	* amd64-linux-nat.c (amd64_linux_fetch_inferior_registers)
>> 	(amd64_linux_store_inferior_registers): Use get_regcache_arch to get 
>> 	at
>> 	the current architecture. Update calls of
>> 	amd64_native_gregset_supplies_p.
>> 	* amd64bsd-nat.c (amd64bsd_fetch_inferior_registers)
>> 	(amd64bsd_store_inferior_registers): Likewise.
> 
> Tested on x86_64-linux, no regression :).
> 

Hi Joel,

thanks a lot !

Regards,
Markus

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


  reply	other threads:[~2008-01-15  4:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 17:13 Markus Deuling
2008-01-12  9:44 ` Joel Brobecker
2008-01-15  4:45   ` Markus Deuling [this message]
2008-01-15 20:41 ` Ulrich Weigand
2008-01-16  4:54   ` 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=478C39D3.9070403@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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