This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: IA32: printing FP register variables
- To: Jim Blandy <jimb@cygnus.com>
- Subject: Re: IA32: printing FP register variables
- From: Jeffrey A Law <law@cygnus.com>
- Date: Sat, 10 Jul 1999 17:15:06 -0600
- cc: "Ben Combee" <bcombee@metrowerks.com>, egcs@egcs.cygnus.com, gdb@sourceware.cygnus.com
- Reply-To: law@cygnus.com
In message <npbtdlsg2i.fsf@zwingli.cygnus.com>you write:
> In code generated by your compiler, is the value of TOP (the three-bit
> FPU stack pointer) at function entry known at compile time? Or does
> its value depend on the caller, and the caller's caller, etc.?
Aren't all the FP registers on the x86 considered call-clobbered? If
so, then there should be no FP regs live across a function call.
With that in mind, the state of the FP stack ought to be empty at the
start of each function.
Or am I missing something? I'm not really an ia32 guru.
jeff