This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFD] How to fix FRAME_CHAIN_VALID redefinition in config/i386/tm-i386v4.h ?

On Sun, Feb 17, 2002 at 11:57:00AM -0500, Andrew Cagney wrote:
> >
> >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.

Right.  Delete that part of the sentence and look at the changing the
value for all targets bit :)

> >>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.

Yep.  COERCE_FLOAT_TO_DOUBLE is also on my hitlist.

Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]