From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13485] ARM incorrect parsing of inlined variables
Date: Fri, 19 Jan 2024 05:04:37 +0000 [thread overview]
Message-ID: <bug-13485-6586-m6VzvQaXy5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13485-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13485
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
CC| |wcohen at redhat dot com
Status|NEW |RESOLVED
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
I manually ran inlinedvars.stp on the last version of Fedora that supported
32-bit arm. It appears to work correctly:
[wcohen@fedora systemtap]$ rpm -q gcc kernel
gcc-12.2.1-4.fc36.armv7hl
kernel-6.2.15-100.fc36.armv7hl
[wcohen@fedora systemtap]$ uname -a
Linux fedora 6.2.15-100.fc36.armv7hl #1 SMP Thu May 11 17:07:19 UTC 2023 armv7l
armv7l armv7l GNU/Linux
[wcohen@fedora systemtap]$ gcc
/home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/inlinedvars.c
-g -lm -o inlinedvars.exe
[wcohen@fedora systemtap]$ sudo ../install/bin/stap
/home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/inlinedvars.stp
inlinedvars.exe -c ./inlinedvars.exe
WARNING: unused command line option $1/@1
call (22,84)
call2 (128,-22)
main (64,42)
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2024-01-19 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 15:05 [Bug translator/13485] New: " wade_farnsworth at mentor dot com
2011-12-08 15:06 ` [Bug translator/13485] " wade_farnsworth at mentor dot com
2011-12-08 15:21 ` wade_farnsworth at mentor dot com
2024-01-19 5:04 ` wcohen 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-13485-6586-m6VzvQaXy5@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).