lkml.org 
[lkml]   [1996]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: No, no no! (#define long int)
Ick.  I'll go over this and try to clean up before the
general release. This C code was created by a FORTRAN to C
translator which was used mostly on Sun and various DSP
chips.

The: #define int long

is defensive programming against 16 bit compilers which
truncate long values which are valid in the LPC-10 code.

>> I'm not quite sure, but it seems to be working fine,
>> better than the last LPC which was doing math errors

If the original PARC LPC code (which remains in the program,
as it is a standard VAT and RTP compression mode) is generating
floating point errors, this indicates that your system is not
masking floating point exceptions and handling them by default.
The LPC code routinely generates floating underflows, which the
FPU should set to zero with no error indication. If you're
getting interrupts for this, your coprocessor support is
enabling interrupts most systems mask.

------- End of Forwarded Message


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.029 / U:1.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site