Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: [PATCH/RFA/RFC] Replecament for DEPRECATED_REG_STRUCT_HAS_ADDR
Date: Sun, 14 Sep 2003 14:11:00 -0000	[thread overview]
Message-ID: <3F64772A.2030207@redhat.com> (raw)
In-Reply-To: <200309141313.h8EDD3um071823@elgar.kettenis.dyndns.org>

> Here is the promised patch to replace DEPRECATED_REG_STRUCT_HAS_ADDR.
> I've baptized the new method stabs_argument_has_addr since that better

like it.

> describes what it does than the old REG_STRUCT_HAS_ADDR; it's also
> used for non-register and non-struct arguments, at least on SPARC.  I
> also dropped the gcc_p argument since none of the current
> implementations of DEPRECATED_REG_STRUCT_HAS_ADDR actually use it.
> 
> Anyway, I moved the type checks that were done in stabsread.c into
> default_stabs_argument_has_addr.  This means that
> stabs_argument_has_addr has to do all type-checks.  On SPARC this is
> needed to support quad-precision floating-point arguments.
> 
> Andrew, I made stabs_argument_has_addr a multi-arch function, and I
> don't provide a macro for it.  Is that all-right?  I'm a bit confused
> when to provide a macro and when not.  What are your current ideas
> about that?  Personally I think we should get rid of the macros and
> explicitly use current_gdbarch.

Yep, thats the intent.

Andrew



  reply	other threads:[~2003-09-14 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-14 13:13 Mark Kettenis
2003-09-14 14:11 ` Andrew Cagney [this message]
2003-09-14 15:57   ` Mark Kettenis
2003-09-16 15:42 ` Elena Zannoni
2003-09-17 21:24   ` Mark Kettenis
2003-09-21 12:26 ` Eli Zaretskii
2003-09-21 19:57   ` Mark Kettenis

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=3F64772A.2030207@redhat.com \
    --to=ac131313@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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