John L. Ries wrote:
On Fri, 24 Feb 2006, Frank Heckenbach wrote:
Waldek Hebisch wrote:
Same feature set where reasonably possible. As earlier GCC versions are already obsolescent (I don't want to drop them immediately, but is there any real need for versions before 3.4 anymore?), we should not waste any effort back-porting things. An error message when trying to use them with an earlier backend should be clear enough, so those who need threads will know they have to use 3.3 or newer.
Actually, I'm still running GCC 2.95 on several of my older UNIX boxes because my efforts to compile newer versions there have failed. Not that I need a new GPC on any of them, but it goes to show 2.95 is still in active use in at least a few places.
That said, I think you can safely drop support for GCC versions prior to 2.95.
Sooner or later support for 2.95 will be dropped -- in fact, probably together with 2.8.1, as many relevant internal differences (mostly the backend memory management) are the same, and we really should get rid of them sometime. So, while it's not urgent yet, you might try, when you find the time, to build newer versions on those machines and report any problems. Which kind of systems are they, BTW? Frank -- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: ACB3 79B2 7EB2 B7A7 EFDE D101 CD02 4C9D 0FE0 E5E8