X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f X-Recipient: djgpp-workers AT delorie DOT com Message-ID: <4F814D71.6040800@iki.fi> Date: Sun, 08 Apr 2012 11:33:53 +0300 From: Andris Pavenis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: Unstability of last builds of GCC References: <4F80ADBB DOT 6080807 AT iki DOT fi> <201204080352 DOT 06448 DOT juan DOT guerrero AT gmx DOT de> In-Reply-To: <201204080352.06448.juan.guerrero@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com On 04/08/2012 04:52 AM, Juan Manuel Guerrero wrote: > Am Samstag, 7. April 2012 schrieb Andris Pavenis: >> I have noticed unstability of last my builds of GCC >> - version 4.6.3 (all languages supported earlier) >> - version 4.7.0 (Ada supported for cross-compiler only >> due to build problems) >> >> I have not tried to build GCC using my build of gcc-4.7.0 >> yet, but using installed version of gcc-4.6.3 causes >> compile to randomly fail in stage1 (compiler complains >> about syntax errors, rerunning causes compiling the same >> file to succeed). It is especially noticeable when >> building gcc-4.7.0. >> >> One could suggest that it could be caused by use >> of binutils-2.22 (most likely suspect is last >> DJGPP COFF format updates). >> >> Stripped executables seems to be less stable. >> The problems can be reproduced both with DJGPP v2.03r2 >> and current CVS (really about 1-2 weeks old) >> >> Building with gcc-4.6.2 seems to work much better. >> >> Andris >> >> > > > Some questions: > - Are you using the last version of binutils-2.22? > The last version is bnu222br2.zip (2012-02-13). Yes. Latest version for both v2.03r2 and v2.04pre. > - Can I build gcc 4.7.0 and/or gcc 4.6.3 on my local > WinXP mashine? I would like to reproduce the issue. Source is available: http://ap1.pp.fi/djgpp/gcc/4.6.3/ http://ap1.pp.fi/djgpp/gcc/4.7.0/ You can try 4.6.3 binaries from there and try to build 4.7.0 to see the problem. Note that You need to edit src/stub/stub.asm to increase the default stack size to something like 1536K. Maybe it would be better to add additional source file and set _stklen there. It also may be needed to change DOS transfer buffer size for make to 24K (I had so on the computer where I did the builds) Also do not mix v2.03 and v2.04 ports of bash when building gcc-4.7.0. One can mix for 4.6.3. For v2.03r2 one must edit Makefile.in in directory libada and set 'LN_S = cp -pr'. > > In the worst case I could provide a new version of binutils 2.22 > with some new environment variable that would allow to disable the > COFF extensions. In that case you could chek if those changes are > really the culprit of the instability. Well. These changes are there because of gcc build. One could perhaps build gcc-4.6.3 without them. I do not know about 4.7.0. All worked OK with 4.6.2 which was built before support of changes in DJGPP COFF format in binutils. I do not see why it should change but of course one can never be completely sure. One could also suspect build of libc, but I did not rebuild it for v2.03 and got problem also there. Andris