www.delorie.com/archives/browse.cgi | search |
From: | pavenis AT lanet DOT lv |
Message-ID: | <B0000098650@stargate.astr.lu.lv> |
To: | "Gisle Vanem" <gvanem AT eunet DOT no>, djgpp AT delorie DOT com |
Date: | Thu, 19 Aug 1999 16:11:52 +0300 |
MIME-Version: | 1.0 |
Subject: | Re: gcc 2.95 and map-file |
In-reply-to: | <011401beea2b$30b898d0$293f8589@gv015029.bgo.nera.no> |
X-mailer: | Pegasus Mail for Win32 (v3.12) |
Reply-To: | djgpp AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On 19 Aug 99, at 12:11, Gisle Vanem wrote: > I've noticed a change in how gcc 2.8.1 and 2.95 handles map-file > options "-Xlinker -M" or "-Wl,--print-map". This used to produce a map-file > printed on 'stdout'. Now it is printed on 'stderr' causing both symbol listing > and error-messages to intermix. Is this really intentional. > collect2 redirects both stdout and stderr from ld to one file and analyzes it before after ld terminates. At end collect2 writes all to stderr. Port of gcc-2.8.1 didn't use collect2 and therefore map was written to stdout. Andris
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |