From: "jlebon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13420] prologue detection fails for function parameters in unoptimized (-g only, no -O) code
Date: Thu, 27 Feb 2014 19:56:00 -0000 [thread overview]
Message-ID: <bug-13420-6586-FS4OcoWAIU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13420-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13420
Jonathan Lebon <jlebon at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jonathan Lebon <jlebon at redhat dot com> ---
I've updated the prologue searching algorithm so that we now pick up both
prologue_end markers (which clang emits) and 0-line advances (which GCC emits).
All the issues in comment 6 are now resolved, as well as the original
cast-scope testcase.
I also tested and tweaked it to work on older kernels/gccs (or at least to not
be less wrong than we were before). In some cases, we do even better there as
well!
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-02-27 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 12:22 [Bug translator/13420] New: prologue detection fails for unoptimized 64bit cast-scope.exp testcase mjw at redhat dot com
2011-11-21 12:44 ` [Bug translator/13420] " mjw at redhat dot com
2011-11-29 17:19 ` mjw at redhat dot com
2011-11-30 16:36 ` mjw at redhat dot com
2013-12-26 12:54 ` [Bug translator/13420] prologue detection fails for function parameters in unoptimized (-g only, no -O) code fche at redhat dot com
2013-12-26 13:04 ` fche at redhat dot com
2014-02-12 16:42 ` jlebon at redhat dot com
2014-02-27 19:56 ` jlebon at redhat dot com [this message]
2014-02-28 20:09 ` jlebon 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-13420-6586-FS4OcoWAIU@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).