unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org, erik.swahn@neurologic.se
Subject: Re: Fix limitations on vector length
Date: Fri, 04 Oct 2002 11:24:11 -0700	[thread overview]
Message-ID: <E17xX7T-0005Sb-00@giblet> (raw)
In-Reply-To: <200206251332.PAA12602@faun.nada.kth.se> (message from Roland Orre on Tue, 25 Jun 2002 15:32:54 +0200 (MET DST))

   From: Roland Orre <orre@nada.kth.se>
   Date: Tue, 25 Jun 2002 15:32:54 +0200 (MET DST)

   Some of our code using multidimensional arrays behaved buggy and that
   showed to be caused by the limitations of vector lengths to 24 bits,
   we need at least a few bits more at the moment.

this limitation should be documented.  (there is mention of string limit
of 2^24 characters (shared implementation), but not for vectors.)

   Problems:
   1) the allocation of the array did not cause an error message.
   2) we need an urgent simple fix for utilizing big arrays.

   What we inted to do is to change the SCM_LENGTH macro and the
   memory allocation for vectors and arrays so when the length
   need more than 24 bits the length is stored in the beginning
   of the array memory, that is we add an offset of four to the
   base pointer.

   Any comments?

did you go through with this plan?  could you supply a diff?  does this
modified guile run on 64 bit machines (alpha, sparc v9)?  any problems
there?

thi


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


      parent reply	other threads:[~2002-10-04 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 13:32 Fix limitations on vector length Roland Orre
2002-06-25 19:50 ` Dirk Herrmann
2002-10-04 18:24 ` Thien-Thi Nguyen [this message]

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E17xX7T-0005Sb-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=erik.swahn@neurologic.se \
    --cc=guile-user@gnu.org \
    --cc=ttn@glug.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).