[fpc-devel]bugs to close

Johannes Berg johannes at sipsolutions.com
Tue Nov 25 12:00:18 CET 2003

> > 2759 - attached is a patch of i386 only. However, wouldn't it be more
> >        appropriate to handle FPU exceptions than checking all
> >        pre-conditions?
> If someone knows how to handle these exceptions correctly, yes.

Well, its platform dependent. On Windows, you get an exception. On
posix, you get SIGFPE (=8). Now, the question is how to handle that
Another possibility would be to mask the FPU exceptions before each
operation, reset the control word after the operation and also check if
an exception occurred. This will probably be slower because there's more
overhead before each FPU call. However, it'll still be far faster than
the current solution.
I'll investigate the signal handling issue(s) and see if its possible to
handle SIGFPE properly.

GnuPG key: http://www.sipsolutions.de/keys/JohannesBerg.asc
  Key-ID: 9AB78CA5 Johannes Berg <johannes at sipsolutions.de>
  Fingerprint = AD02 0176 4E29 C137 1DF6 08D2 FC44 CF86 9AB7 8CA5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20031125/2d71197c/attachment.sig>

More information about the fpc-devel mailing list