delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2003/04/23/08:12:04.2

Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3EA67FE9.E27322C7@phekda.freeserve.co.uk>
Date: Wed, 23 Apr 2003 12:58:33 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: 2.04 status page / 2.04 alpha 1 release schedule
References: <200304231054 DOT MAA07312 AT lws256 DOT lu DOT erisoft DOT se>
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Martin Stromberg wrote:
[snip]
> Issues not specific to DJGPP 2.04, but could be fixed in it
> 
> * The default stack size, 512KB...
> 
>     Now there is an option to stubify to set that. Or are you talking
>     about gxx?

I think the problem was that gcc 3.3 needed a lot of stack space. I think
that's fixed now. See Andris's message "Re: DJGPP 2.04 status page" from Thu,
20 Feb 2003 16:25:55 +0200.

I've marked this item as resolved. Let me know, if anyone thinks it should
still be open.

> * Some DJGPP utilities do not have documentation: symify, go32-v2,
>   stubify, stubedit, exe2coff, dxegen, edebug32 & fsdb. Later: Most of
>   them do now.
> 
>     All the one mentioned do have now.

Thanks, I've moved that to the resolved section.

> * The sources do not build with gcc 3.3, because of its more strict checking...
> 
>     Are you serious about priority 1? 1. That one isn't released
>     yet, right? 2. You can disable it with -Wno-strict-alias, right?
>     3a. Given the buggy behaviour of the first releases of 3.something
>     I'll probably not touch that one for a long time. 3b. I suggest we
>     try to correct more serious problems/missing stuff (but you decide
>     what you want to do on your time). I'd give it 4 or perhaps maybe
>     possibly 3.

Oops, downgraded to priority 2.

gcc 3.3 isn't strictly released yet, but I expect it will be by the time DJGPP
2.04 final comes out. So it should be fixed by then.

Currently only two files fail to build with gcc 3.3. It's probably not a lot
of effort to fix them. Esa Peuha described how to fix it a while back, IIRC.
You're right - I've been spending my time on more important things!

> Resolved Issues
> 
> * remove, select, llseek and fchown don't have any tests.
> 
>   Add strtold().

Added, thanks.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019