From: "jlebon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16615] don't require access to dwarf_query in has_single_line_record()
Date: Thu, 17 Apr 2014 21:56:00 -0000 [thread overview]
Message-ID: <bug-16615-6586-FiuffR6pPL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16615-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16615
Jonathan Lebon <jlebon at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jonathan Lebon <jlebon at redhat dot com> ---
Merged into master.
(In reply to Jonathan Lebon from comment #3)
> We no longer rely on dwarf_getsrc_file(), which is slow, imprecise, and has
> funny behaviours.
Hmmm, that sounded a bit harsh in retrospect. Just to clarify,
dwarf_getsrc_file() does the job, but isn't what we need here. It scours all
CUs for any Dwarf_Lines in the target srcfile, when all we're interested in is
the current CU. This is one of the main reasons it is slower. If no line
records are found for the wanted lineno, it picks the next lineno with line
records. This complicates things for us, since we want to be precise.
These are the reasons why it's not a good fit for what we're trying to achieve
here (but may work well in other situations).
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2014-04-17 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 20:55 [Bug translator/16615] New: " jlebon at redhat dot com
2014-02-20 20:57 ` [Bug translator/16615] " jlebon at redhat dot com
2014-04-08 14:29 ` jlebon at redhat dot com
2014-04-17 18:22 ` jlebon at redhat dot com
2014-04-17 21:56 ` jlebon at redhat dot com [this message]
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=bug-16615-6586-FiuffR6pPL@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).