From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/23634] WARNING: Can't parse SDT_V3 operand for x86_64 qemu tapset probe points
Date: Wed, 12 Sep 2018 14:12:00 -0000 [thread overview]
Message-ID: <bug-23634-6586-GxM8bTTMNq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23634-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23634
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
> Would there be a problem changing the default STAP_SDT_ARG_CONTRAINT from "nor" to "nr"?
Not so easy, unfortunately, or we would've done it already. "nr" forces the
compiler to push nonliteral arguments into registers. There may not be many
registers free at that point in the code, or in the processor generally, so
there are performance costs.
If we can satisfy a systemtap.apps testsuite run with "nr" on x86-64 (not so
register-starved an architecture), then for that one perhaps we can switch the
default, and force people to accept the cost.
The underlying problem here is that in gcc, there seems to be no code that
corresponds to "public symbol relative offset" or "register-relative offset",
both of which we could or do easily support in stap or other consumers. It's
only this "local scratch symbol relative offset" case that's a loser.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-09-12 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 19:12 [Bug translator/23634] New: WARNING: Can't parse SDT_V3 operand for x86_64 qemu shared libraries wcohen at redhat dot com
2018-09-11 19:24 ` [Bug translator/23634] WARNING: Can't parse SDT_V3 operand for x86_64 qemu tapset probe points wcohen at redhat dot com
2018-09-12 14:03 ` wcohen at redhat dot com
2018-09-12 14:12 ` fche at redhat dot com [this message]
2018-09-12 15:03 ` wcohen at redhat dot com
2018-09-12 15:56 ` fche at redhat dot com
2020-02-19 21:07 ` fche at redhat dot com
2021-04-15 15:46 ` dgilbert at redhat dot com
2021-04-19 19:15 ` 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-23634-6586-GxM8bTTMNq@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).