From: pavenis AT lanet DOT lv To: Eli Zaretskii , djgpp-workers AT delorie DOT com Date: Fri, 3 Aug 2001 18:37:40 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Test binaries of gcc-3.0.1 20010802 (prerelease) Message-ID: <3B6AEF74.318.FCAC74@localhost> In-reply-to: <200108031523.LAA31236@delorie.com> References: <3B6AD5E9 DOT 23174 DOT 98E16A AT localhost> (pavenis AT lanet DOT lv) X-mailer: Pegasus Mail for Win32 (v3.12c) 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 On 3 Aug 2001, at 11:23, Eli Zaretskii wrote: > > From: pavenis AT lanet DOT lv > > Date: Fri, 3 Aug 2001 16:48:41 +0300 > > > > http://www.ltn.lv/~pavenis/gcctest.html > > > > I built them using 2001/08/02 CVS version of DJGPP runtime library. > > I still think that it's unwise to use the CVS version of the library > to produce the GCC port. I posted the list of patches to libc.a v2.03 > I think would benefit users on W2K. (Now there's another patch to > crt0.S by Charles.) Maybe it's would be best to put all related patches in a single place to avoid need to collect then from mailing list (otherwise it's very simple to forget some of them) > There's another issue related to GCC 3.0: the register-naming scheme > in the DWARF2 debug info. I'd be interested to hear your opinion; if > you think the current register names should not be changed, I'd like > to make a change in GDB before v5.1 is out (the pretest has just > started). Currently I have put in suggestion Mark sent recently: #undef DBX_REGISTER_NUMBER #define DBX_REGISTER_NUMBER(n) \ ((write_symbols == DWARF2_DEBUG) ? svr4_dbx_register_map[n] : dbx_register_map[n]) But I don't have any objections to leave things as they were (without this addition) One more problem: It seems that -gcoff support have suffered from too serious bitrot: trying to run LAPACK tests with this gcc version run into trouble when GAS (binutils-2.11.2 and also some other recent versions) failed when -g was specified (with -gstabs+ all was Ok) I verified that I have the same problem with gcc-3.0 binaries Andris