From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>,
gdb-patches@sources.redhat.com
Subject: Re: [RFD] How to fix FRAME_CHAIN_VALID redefinition in config/i386/tm-i386v4.h ?
Date: Sun, 17 Feb 2002 08:57:00 -0000 [thread overview]
Message-ID: <3C6FE0DC.1060308@cygnus.com> (raw)
In-Reply-To: <20020217113349.A3217@nevyn.them.org>
>
> Or we could fix this particular problem by making FRAME_CHAIN_VALID
> into a multi-arch method (just in case, and for hppa (?) which seemed
> to have a useful redefinition, though I don't see why it was needed),
> defaulting it to func_frame_chain_valid for all targets. No one ever
> gave me a reason not to do this when I asked.
Er, FRAME_CHAIN_VALID is a multi-arch method.
>> I suspect a combination of the first three is the best. The moment the
>> heuristic is pushed down to the target we end up with inconsistent,
>> target dependant, behavour.
>
>
> There's some interesting code along these lines in what Richard
> committed for ARM. He parses things like glibc's .note.ABI-tag
> section, as well as ELF_OSABI fields where set.
The situtation is very similar to COERCE_FLOAT_TO_DOUBLE. The problem
should be solved in a generic way. However, until then each target gets
to come up with a local solution.
Andrew
next prev parent reply other threads:[~2002-02-17 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-17 5:45 Peter.Schauer
2002-02-17 8:23 ` Andrew Cagney
2002-02-17 8:37 ` Daniel Jacobowitz
2002-02-17 8:57 ` Andrew Cagney [this message]
2002-02-17 8:58 ` Daniel Jacobowitz
2002-02-18 0:44 ` Peter.Schauer
2002-02-18 2:52 ` Richard Earnshaw
2002-02-18 4:02 ` Peter.Schauer
2002-02-18 2:43 ` Richard Earnshaw
2002-02-17 9:23 ` Andrew Cagney
2002-02-18 0:33 ` Peter.Schauer
2002-02-18 6:58 ` Andrew Cagney
2002-02-18 7:57 ` 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=3C6FE0DC.1060308@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
--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