delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com |
Date: | Thu, 29 Jun 2000 10:13:09 -0400 |
MIME-Version: | 1.0 |
Subject: | Re: ANNOUNCE: Binutils 2.10 released |
Message-ID: | <395B2135.18073.1CF437@localhost> |
References: | <Pine DOT A41 DOT 4 DOT 05 DOT 10006271703430 DOT 35992-100000 AT ieva06 DOT lanet DOT lv> |
In-reply-to: | <Pine.SUN.3.91.1000629094336.9718A-100000@is> |
X-mailer: | Pegasus Mail for Win32 (v3.12c) |
Reply-To: | djgpp-workers AT delorie DOT com |
> Can someone say a few words about the reason(s) for this .section > .text change in GCC, and its implications, besides the issue with > Binutils? I changed it so the output of section names would be consistent. That way one could grep for '\.section' in an assembly output and have no trouble finding all the section changes. But it turns out that in C '.text' (and .data and .bss) is still output. As for implications beyond Binutils, I don't think there are any. But the episodes also points gcc 3.0 can output code in sections other than .text (.gnu.linkonce.t.* for example). This just means that the section output macro needs to be changed to add the code attribute to these sections. No big deal. Mark
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |