Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: deuling@de.ibm.com (Markus Deuling), gdb-patches@sourceware.org
Subject: Re: [rfc] [2/6] Replace DEPRECATED_FUNCTION_START_OFFSET
Date: Mon, 18 Jun 2007 20:39:00 -0000	[thread overview]
Message-ID: <200706182038.l5IKcoQI005277@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <u645lrrey.fsf@gnu.org> from "Eli Zaretskii" at Jun 18, 2007 10:31:01 PM

Eli Zaretskii wrote:
> > this patch replaces DEPRECATED_FUNCTION_START_OFFSET by gdbarch_deprecated_function_start_offset. 
> 
> Sorry if I'm missing something obvious (I didn't track this series of
> patches too closely), but what is the purpose and the advantages of
> replacing a deprecated macro with a deprecated function?

The purpose of this patch series is to make the "current_gdbarch" that is
implicit in those macros *explicit* at the call site, so that we can
subsequently replace it with the appropriate local "gdbarch" architecture.
This is all part of supporting multiple architectures at the same time.

Now, for those particular cases where the macro is already deprecated,
we might alternatively just eliminate its use.  However, for this specific
macro some thought is required how that can be done (if at all).  I thought
it made sense to follow through with eliminating all the gdbarch macros
now, even the deprecated ones.  They actual elimination of the deprecated
routines can happen later on just the same.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2007-06-18 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18  9:03 Markus Deuling
2007-06-18 19:31 ` Eli Zaretskii
2007-06-18 20:39   ` Ulrich Weigand [this message]
2007-06-19  5:43     ` Eli Zaretskii
2007-06-19 18:57       ` Jim Blandy

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=200706182038.l5IKcoQI005277@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=deuling@de.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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