Date: Fri, 17 Aug 2001 13:25:57 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: pavenis AT lanet DOT lv Message-Id: <7704-Fri17Aug2001132557+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: sandmann AT clio DOT rice DOT edu, djgpp-workers AT delorie DOT com In-reply-to: <3B7D0F21.25494.2689A4@localhost> (pavenis@lanet.lv) Subject: Re: _open.c commit? (was Re: Selector Exhaustion) References: <10108162209 DOT AA13700 AT clio DOT rice DOT edu> (sandmann AT clio DOT rice DOT edu) <3B7D0F21 DOT 25494 DOT 2689A4 AT localhost> 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: pavenis AT lanet DOT lv > Date: Fri, 17 Aug 2001 12:33:37 +0300 > > > > I think it should be committed and we should ask people to build > > applications (such as Make, RHIDE, and Bash) with it and test it in a > > variety of environments. > > I have built make-3.79.1 with such patch and bootstrapped gcc-3.0.1 > development versions (from CVS) more than once Thanks, that's good to know. > > However, I'd like to see that patch changed so that plain DOS systems > > aren't affected at all. Why slow down systems which don't need that? > > We already have the _windows_major variable that can be used to easily > > test for whether we are on Windows, and _get_dos_version(1) can be > > used for NT/W2K/XP. > > Ok. But I would not like to rely only on Windows presence. One can > try to run DJGPP applications under DOSEMU under Linux and in this > case I have seen descriptors leak (as far as I remeber) at least with > some versions. We may also have bad DPMI providers for DOS which > leaks descriptors. > > So I would prefer to look whether we have good DPMI server. Right. So maybe we should only do that with CWSDPMI. CWSDPMI can be recognized by calling the Get Capabilities function. > About wasted time in Win9X: Perhaps it would be best to build > BASH and MAKE with included descriptor leak workaround and > compare how big is slowdown for example in real configure > scripts and building some packages. I think it's a good idea. In addition to your examples, I'd also try running some of them under GDB, because DPMI calls have a large performance hit there. I realize that speed normally doesn't matter under GDB, but sometimes it does: for example, I always run Emacs under GDB, for the slim possibility that it will crash.