From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Mon, 25 Jun 2001 13:06:43 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: gcc 3.0 released
Message-ID: <3B373763.10622.36D998@localhost>
References: <3B370911 DOT 17498 DOT 50DFA AT localhost>
In-reply-to: <Pine.A41.4.05.10106251716160.46808-100000@ieva06.lanet.lv>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

> One more problem is dxegen failure on gcc-3.0 compiled object files due to
> .comment section (it misinterprets it as unresolved reference).

A .comment section just contains an id that say in effect, "compiled by gcc 
3.0" that takes the place of those 'gcc2_compiled' symbols. gcc 3.0 generates 
an .ident directive with the id and gas puts the text into the .comment 
section. For dxes, we can either lump the section in with all others, or 
discard it since it's only an id string.

> About Eli's initial question. How possible is some change in
> binutils that would make linker script from current djdev incompatible
> with binutils (I think it's unlikely ...) 

I think so too.

If gcc 3.0 does require binutils 2.11, then it seems to me it need not use 
djgpp.djl at all.

Mark