public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: src ChangeLog parse.cxx staptree.cxx staptree. ...
Date: Fri, 22 Dec 2006 02:34:00 -0000 [thread overview]
Message-ID: <20061222023405.11332.qmail@sourceware.org> (raw)
CVSROOT: /cvs/systemtap
Module name: src
Changes by: jistone@sourceware.org 2006-12-22 02:34:05
Modified files:
. : ChangeLog parse.cxx staptree.cxx staptree.h
translate.cxx
Log message:
2006-12-21 Josh Stone <joshua.i.stone@intel.com>
PR 3671
* parse.cxx (parser::parse_global): Allow a maxsize on global arrays.
* staptree.h (struct vardecl): Add the maxsize field.
* staptree.cxx (vardecl::vardecl): Init. maxsize.
(vardecl::set_arity): Don't allow arity 0 when there's a maxsize.
(vardecl::compatible_arity): Ditto.
(vardecl::print): Include maxsize in output.
(target_symbol::print): Ditto.
* translate.cxx (struct mapvar, mapvar::mapvar): Add maxsize.
(mapvar::init): Init maps with the given maxsize if specified, else
keep using MAXMAPENTRIES.
(mapvar::set): Make the error message give the maxsize.
(mapvar::add): Ditto, and check for overflow on pmap add.
(c_unparser::getmap): Pass the maxsize from the vardecl to mapvar.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/ChangeLog.diff?cvsroot=systemtap&r1=1.528&r2=1.529
http://sourceware.org/cgi-bin/cvsweb.cgi/src/parse.cxx.diff?cvsroot=systemtap&r1=1.60&r2=1.61
http://sourceware.org/cgi-bin/cvsweb.cgi/src/staptree.cxx.diff?cvsroot=systemtap&r1=1.54&r2=1.55
http://sourceware.org/cgi-bin/cvsweb.cgi/src/staptree.h.diff?cvsroot=systemtap&r1=1.48&r2=1.49
http://sourceware.org/cgi-bin/cvsweb.cgi/src/translate.cxx.diff?cvsroot=systemtap&r1=1.147&r2=1.148
next reply other threads:[~2006-12-22 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 2:34 jistone [this message]
2007-11-12 21:55 hunt
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=20061222023405.11332.qmail@sourceware.org \
--to=jistone@sourceware.org \
--cc=systemtap-cvs@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).