This is the mail archive of the gdb@sourceware.cygnus.com 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]

Re: store_floating() rewrite (was Re: bug in arm_push_arguments())


> There is no explicit policy in GDB on which operations are allowed to
> lose precision, and which operations are not supposed to lose
> precision.  I think that if we're going to address the issues raised
> here, we must determine such a policy, and document it.

Well, I think the intended policy (which probably isn't 100% true of
the current implementation) is that precision should be kept when it
is possible/feasible to do so, and that otherwise GDB can lose
precision.

That's bad in the sense that the user doesn't get a clear expectation,
but what's the alternative?  Give an error if we would lose precision
(is there even a general enough way to detect this?  I don't see the
machinery for it now)?

P.S. Kevin Buettner's store_floating rewrite looked about right to me
too.

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