From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <10211241749.AA20874@clio.rice.edu> Subject: Re: 2.04 CVS Build plan To: djgpp-workers AT delorie DOT com Date: Sun, 24 Nov 2002 11:49:16 -0600 (CST) In-Reply-To: <002401c2939c$5600cef0$0100a8c0@p4> from "Andrew Cottrell" at Nov 24, 2002 08:31:27 PM X-Mailer: ELM [version 2.5 PL2] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 > If you have any outstanding CVS patches I will be pulling down the code mid > week and then again on Saturday Sydney time, Friday afternoon US time, > Friday midnight UK time. There are two things I'd like to see in V2.04 that we haven't messed with: 1) Resolve the malloc() issue 2) DXE support for importing main image routines We either need to modify our free algorithm with an early out to stop merging blocks if the free list is long, or convert to the new contributed code. We could do a test build with the new malloc() hand inserted to see if most things behave properly. There is also a need to tweak interfaces or change documentation. Given the time limits probably all we could do was test the new base module for a go/no-go decision. The DXE support is really two different pieces - an enhancement to the DXE loader (about 100 bytes of code) which goes in the libc and in each image to be able to fix up DXE references to symbols which exist in the main image. The second part is a new section to DXE images to include the additional information; the dxegen stuff to create it, and some infrastructure to make it easy to use the feature. Given the light (only emu387?) usage of DXEs in the base build, this may be able to wait since almost nothing would test it anyway. The other thing I didn't mention above is C99 compliance. It will be a real shame if we release in 2003 and don't support C99. Would someone *PLEASE* look at what's needed to get there and create a worklist?