* [Bug uprobes/12741] New: rip-relative instruction is not detected as such
@ 2011-05-07 2:01 jistone at redhat dot com
2011-05-07 2:02 ` [Bug uprobes/12741] " jistone at redhat dot com
2011-09-22 1:27 ` jistone at redhat dot com
0 siblings, 2 replies; 3+ messages in thread
From: jistone at redhat dot com @ 2011-05-07 2:01 UTC (permalink / raw)
To: systemtap
http://sourceware.org/bugzilla/show_bug.cgi?id=12741
Summary: rip-relative instruction is not detected as such
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: uprobes
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
On Fedora 15 x86_64, uprobes handle_riprel_insn() is computing need_modrm:0 for
opcode 0x89, when the table says it should be 1. Thus the instruction is not
properly being treated as rip-relative.
I noticed that with gcc 4.6, compiling uprobes gives a few warnings like:
arch/x86/include/asm/bitops.h:319:2: warning: use of memory input
without lvalue in asm operand 1 is deprecated [enabled by default]
That line is the asm statement in variable_test_bit(). The most obvious
difference is that test_bit takes const volatile, and our table is just const.
It has always been thus, but apparently gcc 4.6 cares more about this, and is
generating code differently as a result.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug uprobes/12741] rip-relative instruction is not detected as such
2011-05-07 2:01 [Bug uprobes/12741] New: rip-relative instruction is not detected as such jistone at redhat dot com
@ 2011-05-07 2:02 ` jistone at redhat dot com
2011-09-22 1:27 ` jistone at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: jistone at redhat dot com @ 2011-05-07 2:02 UTC (permalink / raw)
To: systemtap
http://sourceware.org/bugzilla/show_bug.cgi?id=12741
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from Josh Stone <jistone at redhat dot com> 2011-05-07 02:02:15 UTC ---
When our instruction tables are set const volatile to match test_bit(), the
warning goes away, and need_modrm is now computed correctly. Commit 0746c987.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug uprobes/12741] rip-relative instruction is not detected as such
2011-05-07 2:01 [Bug uprobes/12741] New: rip-relative instruction is not detected as such jistone at redhat dot com
2011-05-07 2:02 ` [Bug uprobes/12741] " jistone at redhat dot com
@ 2011-09-22 1:27 ` jistone at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: jistone at redhat dot com @ 2011-09-22 1:27 UTC (permalink / raw)
To: systemtap
http://sourceware.org/bugzilla/show_bug.cgi?id=12741
--- Comment #2 from Josh Stone <jistone at redhat dot com> 2011-09-22 01:26:32 UTC ---
A similar asm warning cropped up in the uprobes patchset going upstream, and
this time I did a fuller analysis of why this warning makes a difference to the
test_bit result. Link for posterity: https://lkml.org/lkml/2011/9/21/470
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-09-22 1:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-05-07 2:01 [Bug uprobes/12741] New: rip-relative instruction is not detected as such jistone at redhat dot com
2011-05-07 2:02 ` [Bug uprobes/12741] " jistone at redhat dot com
2011-09-22 1:27 ` jistone at redhat dot com
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).