public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25346] New: support enum context variables
Date: Sat, 04 Jan 2020 18:20:00 -0000	[thread overview]
Message-ID: <bug-25346-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=25346

            Bug ID: 25346
           Summary: support enum context variables
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: fche at redhat dot com
  Target Milestone: ---

It would be helpful to have stap resolve enum values from the target context:

enum foo { bar, baz };
int main () {}

stap -e 'process.function("main") { println($bar) }'

This can enable a variant of @const that is possible to wrap in an
if(@defined()) guard, and thus provide new compatibility mechanisms.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-01-04 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04 18:20 fche at redhat dot com [this message]
2020-12-18  6:33 ` [Bug translator/25346] " craig.ringer at 2ndquadrant dot com
2020-12-18  6:41 ` craig.ringer at 2ndquadrant dot com
2020-12-18 12:29 ` fweimer at redhat dot com
2021-01-06  0:58 ` craig.ringer at 2ndquadrant dot com
2021-01-08  8:32 ` craig.ringer at 2ndquadrant dot com
2021-01-20 15:21 ` scox at redhat dot com
2021-02-08 18:19 ` scox 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-25346-6586@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).