[j-nsp] force-64bit

Chris Adams cma at cmadams.net
Wed Jun 1 13:57:52 EDT 2016

Once upon a time, Phil Rosenthal <pr at isprime.com> said:
> I suspect that there is not that high of a risk of bugs due to this change, in all likelihood, the only changes required for this was a different compiler and perhaps the use of a few 64 bit instead of 32 bit variables — but even with a low risk of bugs, if there is no benefit, I’m not sure what the point of adding even a low risk of bugs.

Presumably, this is a straight-up recompile.  It is possible that there
was some sloppy coding (most common 32->64 bit conversion problems come
from assuming int and pointer are the same size); that kind of bug
usually gets sorted out pretty rapidly (and would probably be changed in
the common source, not just a 64-bit fork).
Chris Adams <cma at cmadams.net>

More information about the juniper-nsp mailing list