Mail Archives: djgpp-workers/2001/08/21/12:53:17
> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Tue, 21 Aug 2001 09:19:45 -0500 (CDT)
>
> I will create a patch kit for 2.03 as soon as possible.
Thanks!
> I was hoping I had another week. The _creat* patches work, but Eli
> wanted to swap the order and I have not had a chance to create tests
> for this, so they haven't been committed. I think I can back-patch
> everything else very quickly.
It's possible that some of the patches are not relevant for GCC, or
for v2.03 in general. For example, FAT32 is not supported by v2.03,
so the change in _open which removed the FAT32 bit from the BX
register isn't needed. As another example, if GCC doesn't use fstat
or utime, the patches we applied there might not be required for
building it. In fact, if GCC doesn't use any of the functions that
call IOCTL, the code in _open which uses the SFN open function is not
required either.
In general, I'd suggest to patch v2.03 with only those patches which
we _know_ are required (such as the cure for crashes in nested
programs), since the patched code is relatively untested and could in
itself introduce bugs.
Perhaps we should first have a list of patches, and then have a short
discussion about which are relevant. Andris, is it possible to run
`nm' on the programs which are part of the GCC distribution, to see
what library functions are linked in? That might help sorting out the
patches.
- Raw text -