From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13486] pass-4 error (frame_base undeclared), inlined function argument
Date: Thu, 27 Sep 2012 16:53:00 -0000 [thread overview]
Message-ID: <bug-13486-6586-uguzANrhMZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13486-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13486
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #4 from Josh Stone <jistone at redhat dot com> 2012-09-27 16:52:41 UTC ---
(In reply to comment #3)
> I think your patch handles this correctly. But you could consider moving the
> check up into the for (l = loc; l != NULL; l = l->next) loop just above it that
> checks the types. You can probably just check whether to output the frame_base
> at the same time instead of looping through the location chain twice. Although
> the chains aren't very deep, so it probably doesn't matter.
Thanks for checking. I did consider moving it into the loop you mention, but
decided not to for two reasons. First, I didn't want to perturb the relative
order of the addr and frame_base declarations. Second, we only want a single
frame_base declaration, even if multiple parts of the chain use it, so if we
can't break the loop, then another tracking variable is needed. It seems
simpler to add a new loop iteration just for the frame_base.
Pushed as commit b0b86028.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2012-09-27 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 20:15 [Bug translator/13486] New: " fche at redhat dot com
2011-12-08 21:22 ` [Bug translator/13486] " fche at redhat dot com
2012-09-27 0:57 ` jistone at redhat dot com
2012-09-27 8:07 ` mjw at redhat dot com
2012-09-27 16:53 ` jistone 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-13486-6586-uguzANrhMZ@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).