Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
	        Joel Brobecker <brobecker@adacore.com>,
	        Daniel Jacobowitz <drow@false.org>,
	        Maxim Grigoriev <maxim@tensilica.com>
Subject: [rfc] [0/8] Get rid of current_gdbarch
Date: Tue, 09 Oct 2007 11:39:00 -0000	[thread overview]
Message-ID: <470B6819.1070903@de.ibm.com> (raw)

Hi,

this is the next series of 8 mostly mechnical patches to get rid of of some trivial to replace occurences of current_gdbarch. 

Tested by running testuite no x86 and gdb_mbuild. Is this ok?


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





             reply	other threads:[~2007-10-09 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 11:39 Markus Deuling [this message]
2007-10-09 18:34 ` Ulrich Weigand
2007-10-09 18:45   ` Daniel Jacobowitz
2007-10-09 18:54     ` Ulrich Weigand
2007-10-09 19:50   ` Maxim Grigoriev
2007-10-09 19:59     ` Ulrich Weigand
2007-10-10  5:14       ` Markus Deuling
2007-10-10  8:09   ` 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=470B6819.1070903@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=maxim@tensilica.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