public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Martin Hunt <hunt@redhat.com>, systemtap@sourceware.org
Subject: Re: Global constants
Date: Mon, 13 Feb 2006 20:20:00 -0000	[thread overview]
Message-ID: <1139862015.11054.47.camel@localhost.localdomain> (raw)
In-Reply-To: <y0m8xsfrpeu.fsf@ton.toronto.redhat.com>

Hi,

On Mon, 2006-02-13 at 15:10 -0500, Frank Ch. Eigler wrote:

> > Also it would be nice to have a way to declare these constants in
> > embedded C [...]
> > something like
> > %{ const_O_CREAT = O_CREAT; %}
> >   instead of
> > O_CREAT = 64
> 
> One problem with this is that globals, if elided by the optimizer,
> would still have such references within the opaque embedded-C blocks.
> (That's one of the reasons that embedded-C code should not refer to
> systemtap data other than its arguments.)

	Yep, that's why I initially was doing this:

	In translate.cxx:emit_global()

    ---
       o->newline() << "static rwlock_t "
                    << "global_" << c_varname (v->name) << "_lock;";
    +  o->newline() << "#define global_"
    +               << c_varname(v->name) << "_DEFINED 1";
    ---

	and then

    ---
    global O_CREAT

    function init_sys_open_flags () %{
    #ifdef global_O_CREAT_DEFINED
        global_O_CREAT = 64;
    #endif
    %}
    ---

Cheers,
Mark.

  reply	other threads:[~2006-02-13 20:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 17:39 Mark McLoughlin
2006-02-13 19:28 ` Frank Ch. Eigler
2006-02-13 19:40   ` Martin Hunt
2006-02-13 20:10     ` Frank Ch. Eigler
2006-02-13 20:20       ` Mark McLoughlin [this message]
2006-02-13 20:14     ` Mark McLoughlin
2006-02-13 20:22       ` Martin Hunt
2006-02-13 20:44         ` Mark McLoughlin
2006-02-13 21:41           ` Martin Hunt
2006-02-14  8:27             ` Mark McLoughlin
2006-02-13 20:09   ` Mark McLoughlin
2006-02-13 20:13 Stone, Joshua I
2006-02-13 20:46 ` Frank Ch. Eigler
2006-02-13 20:36 Stone, Joshua I
2006-02-13 21:05 ` Frank Ch. Eigler
2006-02-13 21:50 Stone, Joshua I
2006-02-13 23:50 ` Frank Ch. Eigler
2006-02-13 22:12 Stone, Joshua I

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=1139862015.11054.47.camel@localhost.localdomain \
    --to=markmc@redhat.com \
    --cc=fche@redhat.com \
    --cc=hunt@redhat.com \
    --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).