Date: Tue, 21 Aug 2001 19:50:43 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: sandmann AT clio DOT rice DOT edu Message-Id: <2593-Tue21Aug2001195043+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 CC: pavenis AT lanet DOT lv, djgpp-workers AT delorie DOT com, acottrel AT ihug DOT com DOT au In-reply-to: <10108211419.AA15543@clio.rice.edu> (sandmann@clio.rice.edu) Subject: Re: gcc-3.0.1 and Win2k References: <10108211419 DOT AA15543 AT clio DOT rice DOT edu> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > 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.