From: Richard Biener <richard.guenther@gmail.com>
To: David Taylor <dtaylor@emc.com>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org, gdb@sourceware.org
Subject: Re: stabs support in binutils, gcc, and gdb
Date: Thu, 03 Jan 2013 16:42:00 -0000 [thread overview]
Message-ID: <CAFiYyc3ii502TGmhB+EeqqH4tnA1d9StBfRExkFRE3-UF4WNAg@mail.gmail.com> (raw)
In-Reply-To: <12972.1357230104@usendtaylorx2l>
On Thu, Jan 3, 2013 at 5:21 PM, David Taylor <dtaylor@emc.com> wrote:
> What is the status of STABS support?
>
> I know that there is considerably more activity around DWARF than STABS.
> It appears that STABS is largely in maintenance mode. Are there any
> plans to deprecate STABS support? If STABS enhancements were made and
> posted would they be frowned upon? Or would they be reviewed for
> possible inclusion in a future release?
>
> [We have copyright assignments in place for past and future changes to
> BINUTILS, GCC, and GDB -- and it took almost 4 years from start to
> finish -- I do not want to ever have to go through that again with the
> company lawyers! So, paperwork should not be an issue.]
>
> I know that DWARF is more expressive than STABS. And if it didn't cause
> such an explosion in disk space usage, we would probably have switched
> from STABS to DWARF years ago.
>
> Switching to DWARF causes our build products directory (which contains
> *NONE* of the intermediate files) to swell from 1.2 GB to 11.5 GB.
> Ouch! The DWARF ELF files are 8-12 times the size of the STABS ELF
> files.
>
> If the DWARF files were, say, a factor of 2 the size of the STABS files,
> I could probably sell people on switching to DWARF; but, a factor of 8
> to 12 is too much.
The idea was to have a working DWARF -> STABS translator, eventually
as part of binutils.
Richard.
> Thanks.
>
> David
next prev parent reply other threads:[~2013-01-03 16:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 16:22 David Taylor
2013-01-03 16:42 ` Richard Biener [this message]
2013-01-03 16:53 ` Joel Brobecker
2013-01-03 16:56 ` nick clifton
2013-01-04 3:31 ` Doug Evans
2013-01-11 14:53 ` David Taylor
2013-01-11 17:41 ` Doug Evans
2013-01-12 1:55 ` Cary Coutant
2013-01-12 2:17 ` Ian Lance Taylor
2013-01-14 16:06 ` Doug Evans
2013-01-14 19:45 ` Cary Coutant
2013-01-14 16:12 ` Doug Evans
2013-01-14 19:49 ` Jan Kratochvil
2013-01-12 13:26 ` Andreas Schwab
2013-01-14 18:57 ` David Taylor
2013-01-14 22:18 ` Andreas Schwab
2013-01-14 23:41 ` Eric Botcazou
[not found] <12972.1357230104__33958.3243280233$1357230256$gmane$org@usendtaylorx2l>
2013-01-03 17:02 ` Tom Tromey
2013-01-03 20:53 ` David Edelsohn
2013-01-03 21:53 ` Jonas Maebe
2013-01-03 22:02 ` David Edelsohn
2013-01-04 4:12 ` Joel Brobecker
2013-01-04 20:20 ` David Edelsohn
2013-01-05 0:11 ` David Edelsohn
2013-01-05 7:53 ` Joel Brobecker
2013-01-05 13:28 ` David Edelsohn
2013-01-05 14:52 ` Joel Brobecker
2013-01-06 0:26 ` David Edelsohn
2013-01-06 7:00 ` Joel Brobecker
2013-01-08 8:10 ` Joel Brobecker
2013-01-08 14:38 ` David Edelsohn
2013-01-08 14:46 ` Arnaud Charlet
2013-01-08 14:49 ` David Edelsohn
2013-01-08 14:58 ` Arnaud Charlet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFiYyc3ii502TGmhB+EeqqH4tnA1d9StBfRExkFRE3-UF4WNAg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=binutils@sourceware.org \
--cc=dtaylor@emc.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox