public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/12609] Cannot see variable values in partial inlined functions with gcc 4.6
Date: Tue, 17 May 2011 09:21:00 -0000	[thread overview]
Message-ID: <bug-12609-6586-xCSwIf6VIM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12609-6586@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12609

--- Comment #2 from Mark Wielaard <mjw at redhat dot com> 2011-05-17 09:21:09 UTC ---
(In reply to comment #1)
> Mark, is there reason to suspect systemtap here, or is this a pure gcc
> "guality" regression?

A quick looks shows gcc doing partial inlining of foo. Some of the variables
might indeed not be available in the partial inlined version of foo that stap
probes. So it might actually reflect reality in this case of where the probe
gets placed. I think I just filed the testcase to do a deeper analysis of what
is going on.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-05-17  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 10:34 [Bug translator/12609] New: " mjw at redhat dot com
2011-05-16 21:29 ` [Bug translator/12609] " fche at redhat dot com
2011-05-17  9:21 ` mjw at redhat dot com [this message]
2011-05-17  9:28 ` fche at redhat dot com
2011-05-17  9:31 ` mjw at redhat dot com
2020-04-10 14:53 ` fche at redhat dot com
2020-04-11  1:40 ` 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-12609-6586-xCSwIf6VIM@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).