NASM - The Netwide Assembler

NASM Forum => Programming with NASM => Topic started by: stressful on December 19, 2014, 03:32:45 AM

Title: Saving FPU onto stack frame. Is it good?
Post by: stressful on December 19, 2014, 03:32:45 AM

What if i have saved the FPU state on a local stack frame and restore it at later times after other function calls. Will my saved FPU environment be corrupted in-between?

Title: Re: Saving FPU onto stack frame. Is it good?
Post by: Frank Kotler on December 19, 2014, 07:57:56 AM

Should be good until the stack frame is destroyed - barring serious errors in the "other calls".

Best,
Frank

Title: Re: Saving FPU onto stack frame. Is it good?
Post by: stressful on December 19, 2014, 09:19:36 AM

Quote from: Frank Kotler on December 19, 2014, 07:57:56 AM

Should be good until the stack frame is destroyed - barring serious errors in the "other calls".

Best,
Frank

Thanks Frank. I guess making specialized functions to save and restore the FPU is a bad idea. Maybe I'll just use it internally in functions that use them or use static data area.