Fix internal compiler error on "var2 = var1 + 1" patterns This appears to be the correct fix. It was provided by Tormod Volden (debian.tormod@gmail.com). The final commit is substantially different from Tormod's submission mostly due to housecleaning (removing the old patches and updating the README). Tormod's comments follow. The original addhi_mem_1 "insn" instruction pattern /matches/ two memory operands, just with the /constraint/ that these are the same location. A pattern match tells the compiler "you should be able to use this, but you might have to work on it to meet the constraints". For typical constraints on registers the compiler can add "reloads", moving stuff between registers or from memory, until the constraints are met and the instruction can be used. However, in this case, no amount of reloads can make two memory locations the same if they already weren't, so the compiler breaks down and cries "unable to generate reloads". It seems this issue only appears if optimization is enabled. The proof is in gcc's reload.c and is left as an exercise to the reader. Limiting the matching pattern to identical memory operands avoids these situations, while allowing the common "var++" cases. References: The pattern/constraints difference is explained in https://gcc.gnu.org/onlinedocs/gccint/Simple-Constraints.html#index-other-register-constraints-3335

With LWTOOLS 4.0, a substantial reorganization of the project has occurred.
This document serves to explain the reasoning behind the various changes.

The most obvious change is that the gnu auto tools have been eliminated.
While they proved useful for initial distribution of the software,
particularly for construction of the win32 binaries, they have since proved
to add an unacceptable level of complexity to every aspect of development
from merely tinkering with source files to doing complete releases. Thus,
the auto tools have been ditched in favour of specific hand tuned help where
required.

The other substantial change is that the source code repository has been
recreated from scratch. The old repository was full of cruft from various
revision control systems that were used over the years (CVS, Subversion, and
Mercurial). It was felt that starting a new Mercurial repository with a
completely clean slate would simplify matters substantially. Thus, the old
repository now serves as an archive.