- Recent changes in vax_watch.c changed the input parameter from a
physical address to a register address within the watch chip.
- vax630_sysdev.c called the older wtc_wr() with the new parameter,
but the length argument has been removed.
- The watch chip never starts as valid. Make it valid when the TODR is
attached (i.e. reflecting a connected battery).
- 64 bytes of bus addresses for the watch chip can sometimes be dispatched
to wtc_rd() and wtc_wr(). Make sure that reasonable memory is always
referenced for all potential accesses.
- restore vax8200 to makefile which got lost in a prior merge.
Windows 10 1803 or later NTFS filenames are set to be case-sensitive if the Windows Subsystem for Linux (WSL) feature is turned-on. This was causing a build under cygwin 3.0.1 to fail detecting the libpcap header and library locations in the ../windows-build/libpcap directory.
- OS X libpcreposix segfaults when a compiled regular expression is freed.
- Revise regular expression syntax used in VAX diagnostic scripts to avoid
Perl oriented extensions.
- Diagnostic execution happens as a normal part of the makefile build.
- Diagnostic execution can be suppressed by invoking make with TESTS=0
on the command line
- Diagnostic execution during build is produced in summary form.
- clang's list of optimization options makes no mention of strict-overflow
or no-strict-overflow, but it silently accepts -fno-strict-overflow and
in fact honors it.
The VAX simulator is counting on undefined C language behaviors
which allow the optimizer to correctly produce unexpected results.
Hopefully this will be sufficient until the VAX architecture verifier
(AXE) can be found to validate a rewritten simulator.
As reported in #598
- Fixed screen alignments/scrolling between commands
- Add ncurses screen update support on non-windows platforms
- Add tests for new frontpanel APIs
- Add multiple panel startup and shutdown activity to test shutdown
- Add breakpoints to help debug VAX console ROM tests that have failed
These include simulators for the IBM 701, IBM 702, IBM 704, IBM 705,
IBM 705/3, IBM 709, IBM 1410/IBM 7010, IBM 7070, IBM 7080, IBM 7090
and IBM7094.
These basically were a collection of machines that shared a common
set it peripherals, Each group had its own instruction set, hence
different simulators.
IBM 701 -> i701
IBM 702/705/705/3/7080 -> i7080
IBM 7070/7074 -> i7070
IBM 1410/7010 -> i7010
IBM 704 -> i704
IBM 704/709/7090/7094 -> i7090
The i7090 can be set to simulate a IBM 704 however you end up
disabling almost everything, since the 704 did not have any channels.
A build option exists that allows this one to be built without all the
extra features.
The i7090 simulator’s implementation of the IBM 7094 is a more
complete implementation of the IBM 7094 which can run CTSS
while the existing simh I7094 can’t.
