From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com, dan@debian.org
Subject: Re: REG_STRUCT_HAS_ADDR
Date: Sat, 13 Sep 2003 15:01:00 -0000 [thread overview]
Message-ID: <3F633132.4050603@redhat.com> (raw)
In-Reply-To: <200309131425.h8DEP6ZF012300@elgar.kettenis.dyndns.org>
> That's a good strategy. However, making this stabs-specific seems
> wrong to me. The new method will simply indicate whether the ABI
> silently uses pass by reference instead of pass by value for function
> argument of a certain type. Therefore I don't think we should put
> STABS in the name. What about PASS_ARGUMENT_BY_REFERENCE? I'm going
> to drop the GCC_P argument too, since nobody is using it. I'll post a
> patch later today.
To correctly determine if an arument is passed by reference requires the
complete function prototype (same problem as push dummy call). I think,
rather than change the interface (will anyone actually fix/use that
info?) this method should be burried as stabs only. Leave the problem
of defining/implementing a new interface to someone that needs it.
Andrew
prev parent reply other threads:[~2003-09-13 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 22:06 REG_STRUCT_HAS_ADDR Mark Kettenis
2003-09-08 18:43 ` REG_STRUCT_HAS_ADDR Andrew Cagney
2003-09-13 14:25 ` REG_STRUCT_HAS_ADDR Mark Kettenis
2003-09-13 15:01 ` Andrew Cagney [this message]
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=3F633132.4050603@redhat.com \
--to=ac131313@redhat.com \
--cc=dan@debian.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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).