public inbox for
 help / color / mirror / Atom feed
From: Jan Kratochvil <>
To: Mark Wielaard <>
Cc: Project Archer <>
Subject: Re: gcc dwarf2out: Drop the size + performance overhead of DW_AT_sibling
Date: Tue, 18 Oct 2011 09:49:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 18 Oct 2011 11:44:57 +0200, Jan Kratochvil wrote:
> The problem is the DIEs skipping by CPU is so cheap on current CPUs it cannot
> be compared with the overhead of providing the helper data for it.  I did not
> expect dropping DW_AT_sibling would be even a consumer performance
> _improvement_.  I expected more it will be either not measurable or just not
> significant enough for the .debug on-disk sizes cost justification.

maybe it could be worth tune out specific special cases where DW_AT_sibling
skips larger set of DIEs and any of the consumers benefits from that case.

Just at least in the case of GDB there are so many several orders of magnitude
worse performance issues than reading out the CU data that I do not think it
matters much and the on-disk size should be the primary concern even even if
would mean some performance degradation, which will not be much measurable.

It is true systemtap is a different kind of consumer, thanks for pointing it


  reply	other threads:[~2011-10-18  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
2011-10-18  9:45     ` Jan Kratochvil
2011-10-18  9:49       ` Jan Kratochvil [this message]
2011-10-19  9:34       ` Mark Wielaard
2011-10-19 11:29         ` Jan Kratochvil
2011-10-19 15:38         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).