Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] Eliminate supply_gregset etc. from -tdep files
Date: Sun, 29 Apr 2007 20:11:00 -0000	[thread overview]
Message-ID: <200704291952.l3TJqIvm031115@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070429164613.GB27509@caradoc.them.org> from "Daniel Jacobowitz" at Apr 29, 2007 12:46:13 PM

Daniel Jacobowitz wrote:
> On Sun, Apr 29, 2007 at 06:18:24PM +0200, Ulrich Weigand wrote:
> > there are two -tdep files (m68k-tdep.c and mips-linux-tdep.c) that contain
> > implementations of the supply_greget family of functions.  This is incorrect;
> > those function should only ever be provided by native support files.
> 
> "Incorrect" may be a bit strong.  core-regset.c needs them to link; at
> one point, that was the right way to implement core file support.  I
> don't remember how the history worked out for mips, since it doesn't
> look like the version in the FSF repository ever used core-regset.o,
> but I think that was the original motivation.

Right, but I thought core-regset.o was also supposed to used only as a 
native support file, never in an .mt file.  Was this ever done in the
past?

Anyway, the reason why I'd like to get of the use in -tdep files is that
it would prevent building GDB with multiple architecture targets built-in
at the same time, if multiple tdep files define different copies of
routines with the same name ...

(B.t.w. it doesn't look too hard to get completely rid of core-regset.o
at this time, but it would need someone to test on i386-gnu, alpha-freebsd,
sparc-solaris ...   I can take care of ia64-linux.)

> Anyway, now there are no targets that use core-regset.o in .mt files,
> and no good reason to do so.  So now it's incorrect :-)  This patch is
> OK.

Thanks, committed.

Bye,
Ulrich

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


  reply	other threads:[~2007-04-29 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-29 16:37 Ulrich Weigand
2007-04-29 17:15 ` Daniel Jacobowitz
2007-04-29 20:11   ` Ulrich Weigand [this message]
2007-04-30 12:27     ` Daniel Jacobowitz

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=200704291952.l3TJqIvm031115@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=drow@false.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