From: Tristan Gingold <gingold@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [patch] dwarf2out: Drop the size + performance overhead of DW_AT_sibling
Date: Tue, 18 Oct 2011 08:39:00 -0000 [thread overview]
Message-ID: <B3CD2835-0260-4A6C-8141-C8570A44CEBD@adacore.com> (raw)
In-Reply-To: <m3aa8zdahf.fsf@fleche.redhat.com>
On Oct 17, 2011, at 3:16 PM, Tom Tromey wrote:
>>>>>> "Tristan" == Tristan Gingold <gingold@adacore.com> writes:
>
> Tom> Another way to look at it is that there have been many changes to GCC's
> Tom> DWARF output in the last few years. Surely these have broken these
> Tom> DWARF consumers more than this change possibly could.
>
> Tristan> Yes, but there is -gstrict-dwarf to stay compatible with old behavior.
>
> Yes, but this change is strictly compliant.
Agreed.
> What makes it different
> from any other change that was made to make GCC more compliant?
> Hypothetical consumers could also break on those changes.
The others changes were often corner cases, while this one is very visible.
What is wrong with my suggestion of adding a command line option to keep the siblings ? This option could be removed in a few years if nobody complained about sibling removal.
Tristan.
next prev parent reply other threads:[~2011-10-18 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 14:18 Jan Kratochvil
2011-10-12 14:59 ` Tristan Gingold
2011-10-12 15:28 ` Jan Kratochvil
2011-10-13 21:16 ` Jan Kratochvil
2011-10-14 9:36 ` Tristan Gingold
2011-10-14 14:18 ` Tom Tromey
2011-10-17 9:44 ` Tristan Gingold
2011-10-17 13:42 ` Tom Tromey
2011-10-18 8:39 ` Tristan Gingold [this message]
2011-10-18 9:03 ` [patch#2] " Jan Kratochvil
2011-10-18 9:04 ` Jakub Jelinek
2011-10-20 15:13 ` Jan Kratochvil
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=B3CD2835-0260-4A6C-8141-C8570A44CEBD@adacore.com \
--to=gingold@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).