This change adds support for the WE32106 Math Acceleration Unit (MAU).
The WE32106 is an IEEE-754 1985 compatible floating point math
acceleration unit that was an optional component on the 3B2/310 and
3B2/400.
The MAU is implemented using software floating point routines. As
always, there may be bugs, but the MAU currently passes extensive
floating point tests with exactly the same results as a real 3B2/400
equipped with a physical MAU, so I hope these are few.
The I650 simulator depends on the sim_card library which had API chages that
the author agreed to before the changes were committed, but no update of the
I650 simulator code has come for the past 2 months.
When git is available, remove manual steps to maintain and update the
windows-build support even for cases where windows-build may have
previously extracted from a downloaded zip file.
Some git capable environments on Windows don't honor the installed git
hook scripts in the repository. Now that, if we're working within a git repo,
we force a working version of git to be installed in the runtime path. We
leverage that to force a validation of the commit id on each build.
- All projects use identical include directories, library definitions and
library directories.
- Remove attempts to add XP support to projects that were converted to
.vcxproj for post VC2008 versions of Visual Studio.
- Require that git be available when building within a git repository
working directory.
- New Commit-Id with Commit-Time
- Properly execute when the Win32-Development-Binaries needs to be cloned
- Properly limit parallel builds if the local system has more than 8 Threads
When the git hooks have changed and git isn't in the path, the correct git
commit id can't be determined and thus be available to be included in
the build. This change announces that fact and stops a build.
This only happens if git is installed locally and available in the current
path when Visual Studio executes. Whether git is in the path is an
installation option when git for Windows is installed.
Otherwise, proper results should be available after subsequent
activity on the local repository. Any build will install the git hooks
that properly populate .git-commit-id when any changes are made
to the local repo.
