From: Andrew Cagney <ac131313@cygnus.com>
To: "David S. Miller" <davem@redhat.com>
Cc: mec@shout.net, fnasser@redhat.com, cagney@cygnus.com,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix xfail Sparc pattern
Date: Thu, 18 Apr 2002 16:25:00 -0000 [thread overview]
Message-ID: <3CBF55DF.4010007@cygnus.com> (raw)
In-Reply-To: <20020418.152834.121227947.davem@redhat.com>
> What I am referring to more specifically is the dummy frame
> descriptors which the generic dummy frame support creates and
> keeps track of. That is generic, and independant of the
> CALL_DUMMY mechanism a target uses.
>
> That aspect is perfect, and I implemented something similar in my
> sparc patches. That bit of the generic dummy frame bits could be
> reused instead of duplicating such state tracking in sparc specific
> code.
>
> Isn't it possible to use ON_STACK for dummy frames and still use
> the dummy frame tracking support provided by generic dummy frames?
> I don't see anything specific to the CALL_DUMMY mechanism used in
> those structures.
Yes, that is the theory. See the very recent patch:
[RFA] Save the call dummy address
http://sources.redhat.com/ml/gdb-patches/2002-04/msg00501.html
Andrew
next prev parent reply other threads:[~2002-04-18 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 9:06 Michael Elizabeth Chastain
2002-04-18 9:21 ` Andrew Cagney
2002-04-18 15:04 ` David S. Miller
2002-04-18 15:29 ` Andrew Cagney
2002-04-18 15:37 ` David S. Miller
2002-04-18 16:25 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-17 12:57 David S. Miller
2002-04-18 7:48 ` Fernando Nasser
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=3CBF55DF.4010007@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cagney@cygnus.com \
--cc=davem@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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