Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Nicholas Duffek <nsd@redhat.com>, gdb-patches@sourceware.cygnus.com
Cc: ezannoni@cygnus.com, phdm@macqel.be, kevinb@cygnus.com,
	Peter.Schauer@regent.e-technik.tu-muenchen.de, jimb@cygnus.com
Subject: Re: [RFA] patch to skip bigtoc fixup code
Date: Tue, 01 May 2001 08:07:00 -0000	[thread overview]
Message-ID: <1010501150355.ZM588@ocotillo.lan> (raw)
In-Reply-To: <200104301626.MAA00208@nog.bosbc.com>

On Apr 30, 12:26pm, Nicholas Duffek wrote:

> 	* config/rs6000/tm-rs6000.h (IN_SOLIB_RETURN_TRAMPOLINE): Define.
> 	(rs6000_in_solib_return_trampoline): Declare.
> 	* rs6000-tdep.c (rs6000_in_solib_return_trampoline): New
> 	function.
> 	(rs6000_skip_trampoline_code): Skip bigtoc fixup code.
> 	* xcoffread.c (read_xcoff_symtab): Perform the ISFCN function
> 	check after the CSECT check rather than before it.  Allocate
> 	separate symtabs for CSECTs whose names begin with '@'.
> 	(scan_xcoff_symtab): Don't ignore symbols beginning with '@'.
> 	Activate the misc_func_recorded mechanism for whose names begin
> 	with '@'.
> 
> Tested on powerpc-ibm-aix4.3.3.0.  Okay to apply?

Nick,

It all looks okay to me.  The tm-rs6000.h and rs6000-tdep.c changes
are approved.  (Actually, I'm not sure you need my approval, since it
looks to me like you're a co-maintainer of these files.)  I'm going to
defer to the others regarding xcoffread.c since I apparently stepped
on a few toes the last time...

I will note, however, that IN_SOLIB_RETURN_TRAMPOLINE ought to be
multiarched at some point, but I see no reason to hold up this patch
since you're merely making use of an existing macro that hasn't yet
been multiarched.

Kevin


       reply	other threads:[~2001-05-01  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200104301626.MAA00208@nog.bosbc.com>
2001-05-01  8:07 ` Kevin Buettner [this message]
2001-05-01 10:28 ` Elena Zannoni
2001-05-01 12:41   ` Nick Duffek

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=1010501150355.ZM588@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=jimb@cygnus.com \
    --cc=nsd@redhat.com \
    --cc=phdm@macqel.be \
    /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