Hi,
On Fri, 17 Dec 2004, 4:03pm -0000, [log in to unmask] wrote:
> -------------- Original message ----------------------
> From: Jouni Lerssi <[log in to unmask]>
> > *** Arithmetic exception: Floating divide by zero - aborting
> In general, problems like this with one compiler and not with others
> are due to some sort of programming error.
In my experience, they're more often due to the way IEEE exception
handling is specified when the code is compiled (or -- when runtime
specification is available -- run).
Is it possible that with -dusty, NAG disables IEEE exception
handling, and that IEEE exception handling is on with other
compilers? It might be that the code itself, knowingly or
unknowingly, handles Infs gracefully when IEEE is on.
What Dick said about memory layouts being different in different
implementations is true; but in my experience, errors involving
illegal memory access are far more likely to lead to segementation
faults than to arithmetic exceptions. (But I'm certainly not
saying that arithmetic exceptions cannot be due to this.)
-P.
--
Peter S. Shenkin Schrodinger, Inc.
VP, Software Development 120 W. 45th St., 32nd Floor
646 366 9555 x111 Tel New York, NY 10036
646 366 9550 FAX USERID: shenkin
http://www.schrodinger.com DOMAIN: schrodinger DOT com
Pre-arranged conf. calls: 816-650-0812 or 888-667-9995; passcode 060428#
|