public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Adam Fedor <fedor@doc.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: objc-lang.c portability (Was Re: [PATCH] Step over Objective-C dispatch function)
Date: Wed, 26 Mar 2003 23:35:00 -0000	[thread overview]
Message-ID: <20030326233553.GA30284@nevyn.them.org> (raw)
In-Reply-To: <0E3D4316-5FE3-11D7-8F82-000A277AC1A4@doc.com>

On Wed, Mar 26, 2003 at 04:31:23PM -0700, Adam Fedor wrote:
> 
> On Thursday, March 20, 2003, at 02:08 PM, Andrew Cagney wrote:
> >
> >I've looked at what the underlying code is trying to do and, 
> >unfortunatly, the original objc-lang.c botched its portability(1), 
> >sigh!  The file is currently native only so infrun.c can't directly 
> >refer to objc-lang.c, and hence, will need to go via a dispatch table. 
> > Going via a dispatch table wouldn't hurt anyway.
> >
> >(1) I noticed that the parameter extract methods assume host=target.
> >
> 
> I'm wondering what's not portable with objc-lang.c? With the remaining 
> patches I have that require this, I was thinking it might be easier to 
> just fix it now. The alternative appears to be adding a whole bunch of 
> things to the language_defn structure. I admit I don't really 
> understand the problem though.

At the very least FETCH_ARGUMENT and CONVERT_FUNCPTR need to go into
the architecture vector.  They're completely incorrect:
  - they assume host == target
  - they will prevent GDB from compiling on host !< {i386, ppc, sparc, hppa}

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-03-26 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E7A2DCA.6050205@redhat.com>
2003-03-26 23:31 ` Adam Fedor
2003-03-26 23:35   ` Daniel Jacobowitz [this message]
2003-03-27 15:53   ` Andrew Cagney

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=20030326233553.GA30284@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=fedor@doc.com \
    --cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).