From: Tom Tromey <tromey@redhat.com>
To: Tristan Gingold <gingold@adacore.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: Mon, 17 Oct 2011 13:42:00 -0000 [thread overview]
Message-ID: <m3aa8zdahf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <C008C4BF-6232-4D30-9E8C-123B24F454DB@adacore.com> (Tristan Gingold's message of "Mon, 17 Oct 2011 09:20:55 +0200")
>>>>> "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. What makes it different
from any other change that was made to make GCC more compliant?
Hypothetical consumers could also break on those changes.
Tom
next prev parent reply other threads:[~2011-10-17 13:17 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 [this message]
2011-10-18 8:39 ` Tristan Gingold
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=m3aa8zdahf.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=jan.kratochvil@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).