Craig A. Berry wrote:
If you get no
indication whatsoever that something misfired under the hood, that's
worth noting. What happens of you do this with your D_FLOAT compiled perl:
$ perl -e "$x = 1.36514538e67; print $x;" $ show symbol $status
Perl just exits to DCL. $STATUS is %X1000048C which translates to 'Arithmetic trap, floating overflow'. My /G_FLOAT build is running now on SIMH. I'll see how it works tomorrow but I suspect it will be the same.
Anyway, I reconfigured and rebuilt with /G_FLOAT today and op/pack.t passes but some other tests are now failing. On Monday I'll compare the results of the first build with the results of the /G_FLOAT build to see what changed. The tests hadn't completed before I left work today (3:43 to build, will probably take as long to test).
Perl has gotten very big, so it does take a very long time to build and test on older hardware.
Gonna take even longer on SIMH. The 3:43 was on a 4000/600. SIMH performs like a MicroVAX II on my Athlon-XP 1600. Disk I/O is pretty fast though being mostly satisfied from the linux disk cache.
