delorie.com/archives/browse.cgi | search |
Date: | Sun, 07 Jan 2001 20:38:02 +0200 |
From: | "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> |
Sender: | halo1 AT zahav DOT net DOT il |
To: | "Mark E." <snowball3 AT bigfoot DOT com> |
Message-Id: | <8011-Sun07Jan2001203800+0200-eliz@is.elta.co.il> |
X-Mailer: | Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 |
CC: | djgpp-workers AT delorie DOT com |
In-reply-to: | <3A586855.22721.66BDCF@localhost> (snowball3@bigfoot.com) |
Subject: | Re: Backslashes in debug info |
References: | <3A585ADA DOT 250 DOT 321507 AT localhost> (snowball3 AT bigfoot DOT com) <3A586855 DOT 22721 DOT 66BDCF AT localhost> |
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 |
> From: "Mark E." <snowball3 AT bigfoot DOT com> > Date: Sun, 7 Jan 2001 13:00:05 -0500 > > One reason is the BFD assembler can handle as many sections as memory allows > while the non-BFD can only handle a very small number of sections (about 40 I > think). Unique sections generated by gcc (like .gnu.linkonce.* in C++) can > easily reach this limit in one source file. Another reason is the generic > dwarf2 support in gas now can be used only by the BFD assembler. Thanks. I guess I'm confused by the name "BFD assembler". From your description, it sounds like it's simply an improved assembler, but instead of developing the old code, it was rewritten from scratch, more or less? Is that right?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |