From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25346] support enum context variables
Date: Fri, 18 Dec 2020 06:33:18 +0000 [thread overview]
Message-ID: <bug-25346-6586-XHD2iC8ygC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25346-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25346
Craig Ringer <craig.ringer at 2ndquadrant dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |craig.ringer at 2ndquadrant dot co
| |m
--- Comment #1 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
Created attachment 13061
--> https://sourceware.org/bugzilla/attachment.cgi?id=13061&action=edit
WIP @enum support
Here's the WIP I have on @enum support
I got pretty bogged on it, and don't expect to be able to progress any time
soon, but maybe it'll help someone else.
When working on it, I found it quite hard to unravel the various visitors and
what they were for, what exactly they implemented etc. There are some
semi-related comments scattered through the patch where I added notes on things
I was trying to understand.
The main interesting bits are dwflpp::iterate_over_enumerations and
dwarf_atenum_query
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-12-18 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 18:20 [Bug translator/25346] New: " fche at redhat dot com
2020-12-18 6:33 ` craig.ringer at 2ndquadrant dot com [this message]
2020-12-18 6:41 ` [Bug translator/25346] " 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-XHD2iC8ygC@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).