This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/20136] Use the @const() operator across the tapset scripts.
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 24 May 2016 18:35:12 +0000
- Subject: [Bug tapsets/20136] Use the @const() operator across the tapset scripts.
- Auto-submitted: auto-generated
- References: <bug-20136-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20136
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
I wonder if this weird phenomenon could be corrected by a simplification of the
way @const() is implemented. What if it were purely a parse-time syntax, that
the parser itself expanded to an embedded_expr %{ ... %} business? So the
staptree.* stuff wouldn't need a const_op machinery at all; your test case
would just work (tm) since post-pass-1, the elaboration code can't even see
@const.
--
You are receiving this mail because:
You are the assignee for the bug.