From: "jlebon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/6941] better prologue heuristics needed for userspace (non-regparm)
Date: Fri, 28 Feb 2014 19:10:00 -0000 [thread overview]
Message-ID: <bug-6941-6586-ZRdLLfVp9E@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-6941-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=6941
Jonathan Lebon <jlebon at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jlebon at redhat dot com
Resolution|--- |FIXED
--- Comment #4 from Jonathan Lebon <jlebon at redhat dot com> ---
> With gcc VTA, prologue searching at -O2 is becoming unnecessary. However,
> at -O0 it is becoming essential, for gcc does not run VTA processing at -O0,
> and the dwarf location list data it emits is only accurate in the
> post-prologue section. So we need to figure out whether the given target
> executable was built with -O0, and then perform proper prologue search
> heuristics.
The code now runs the prologue searching heuristics only for programs that were
not optimized (or for which there may be reasons to believe location info in
their prologues may be unreliable, such as in older GCC versions). See also the
related PR13420.
Commits 277a2b9 and b5b9879.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-02-28 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-6941-6586@http.sourceware.org/bugzilla/>
2012-06-16 16:13 ` fche at redhat dot com
2012-06-16 16:33 ` fche at redhat dot com
2014-02-28 19:10 ` jlebon at redhat dot com [this message]
2008-10-04 0:18 [Bug translator/6941] New: " fche at redhat dot com
2008-10-07 14:37 ` [Bug translator/6941] " fche at redhat dot com
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-6941-6586-ZRdLLfVp9E@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).