Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] PUSH_ARGUMENTS() -> push_dummy_call()
Date: Tue, 25 Mar 2003 20:05:00 -0000	[thread overview]
Message-ID: <3E80B679.6030801@redhat.com> (raw)
In-Reply-To: <20030324173353.GA23605@nevyn.them.org>

> Is it too much overhead/PITA to restructure it so that we can use that
>> >information?  If so I'll probably need to add a new architecture method
>> >to get ths sort of information.
> 
>> 
>> It is definitly beyond the scope of these cleanups.  The interface is 
>> going to be sufficiently different to need a new architecture method anyway.
>> 
>> Would a FETCH_POINTER_ARGUMENT() method be sufficient for your immediate 
>> needs?
> 
> 
> Yes!  Thanks for the pointer.  I'll put together a patch to move it
> into the architecture vector, for those architectures where it has a
> clear implementation.  And try to write up some mostly-accurate
> documentation for what it does...
> 
> Basically, it should work as long as the previous N arguments were all
> pointers, and for reasonably small values of N (objc-lang never goes
> above N == 2 I think).

Yes.  BTW, the method will need a type parameter similar to 
extract_typed_address().

Andrew



  reply	other threads:[~2003-03-25 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24  5:28 Andrew Cagney
2003-03-24 14:19 ` Daniel Jacobowitz
2003-03-24 17:04   ` Andrew Cagney
2003-03-24 17:33     ` Daniel Jacobowitz
2003-03-25 20:05       ` Andrew Cagney [this message]
2003-03-24 18:18 ` Eli Zaretskii
2003-03-26 22:41   ` 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=3E80B679.6030801@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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