delorie.com/archives/browse.cgi | search |
From: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
To: | <djgpp-workers AT delorie DOT com> |
Subject: | Re: gcc 3.0 released |
Date: | Mon, 25 Jun 2001 17:35:17 +0200 |
Message-ID: | <CAEGKOHJKAAFPKOCLHDIMEMCCEAA.tim.van.holder@pandora.be> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) |
In-Reply-To: | <Pine.A41.4.05.10106251716160.46808-100000@ieva06.lanet.lv> |
Importance: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4133.2400 |
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 |
> One more problem is dxegen failure on gcc-3.0 compiled object files due to > .comment section (it misinterprets it as unresolved reference). In last > time I patched dxegen.c to workaround this problem (ignore .comment), but > I'm almost sure Eli would not like such patch I recall having a similar problem with .stab* sections, though that was mostly due to ld -S not stripping the debug info. I would say that it is not a bad thing for dxegen to drop sections it doesn't know about (as long as it gives a decent warning).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |