Hello,
The CVS build is running much better than latest snapshot (20080503_1030).
I'm using OpenVMS 8.3 latest cvs build on Ubuntu 10.04, using putty (telnet), logged-in on two consoles. (the network (TCP/IP) is up on the es40 side. but I don't yet know what must be done network-wise on the host side. anyway, I don't need the network currently.)
Except for some (mostly S-)floating point issues, all of my many own test programs I tried so far now work. I also heavily used the linker without problems. The analyze/disk/repair now no longer reports strange errors and was even able to fix the few which were correctly reported. Only once in the middle of a long session I got an access violation (see below), but when I retried, it worked.
Only once during a long test session I got an access violation*, but when I retried immediately, it worked.
I strongly believe the fix reported in http://www.es40.org/Project_Status
"16-MAR-2009: David Hittner has fixed a problem in the CPU's handling of super-page bits."
helped a lot to get rid of these access violations**. Thank you! Maybe there's another 'malvolent' bit hiding somewhere.
So please David, if you have an idea…
I'll try to fix the floating the few remaining point errors and then run more tests programs.
Hello,
The CVS build is running much better than latest snapshot (20080503_1030).
I'm using OpenVMS 8.3 latest cvs build on Ubuntu 10.04, using putty (telnet), logged-in on two consoles. (the network (TCP/IP) is up on the es40 side. but I don't yet know what must be done network-wise on the host side. anyway, I don't need the network currently.)
Except for some (mostly S-)floating point issues, all of my many own test programs I tried so far now work. I also heavily used the linker without problems. The analyze/disk/repair now no longer reports strange errors and was even able to fix the few which were correctly reported. Only once in the middle of a long session I got an access violation (see below), but when I retried, it worked.
Only once during a long test session I got an access violation*, but when I retried immediately, it worked.
I strongly believe the fix reported in http://www.es40.org/Project_Status
"16-MAR-2009: David Hittner has fixed a problem in the CPU's handling of super-page bits."
helped a lot to get rid of these access violations**. Thank you! Maybe there's another 'malvolent' bit hiding somewhere.
So please David, if you have an idea…
I'll try to fix the floating the few remaining point errors and then run more tests programs.
Best regards,
scruty
*)
**) it's one of those access violation I talked about in my project review here, 2 weeks ago:
http://sourceforge.net/projects/es40/reviews/