public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mmlnx at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/3671] New: Support array size declarations
Date: Wed, 06 Dec 2006 23:51:00 -0000	[thread overview]
Message-ID: <20061206232852.3671.mmlnx@us.ibm.com> (raw)

Forcing every array be MAXMAPENTRIES in size is too restrictive and wasteful. 
If I know ahead of time how many elements I need I should be able to declare an
array of that size.  Right now if I need a mix of small and large arrays, I must
make sure MAXMAPENTRIES can accomodate the largest size needed, forcing all
arrays to be that size.

I realize this has been considered and may be difficult to implement. I still
think it's important to fix.  I ended up implementing some arrays in embedded C
in the socket tapset for this very reason (trying to keep the size down), not a
practice we want to encourage for script writers.

-- 
           Summary: Support array size declarations
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mmlnx at us dot ibm dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=3671

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

             reply	other threads:[~2006-12-06 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 23:51 mmlnx at us dot ibm dot com [this message]
2006-12-06 23:51 ` [Bug translator/3671] " fche at redhat dot com
2006-12-07  1:47   ` Vara Prasad
2006-12-07  2:36 ` prasadav at us dot ibm dot com
2006-12-22 10:46 ` joshua dot i dot stone at intel 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=20061206232852.3671.mmlnx@us.ibm.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /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).