From: Rob Browning <rlb@defaultvalue.org>
Subject: Uniform vector lengths -- how long?
Date: Sun, 20 Jun 2004 16:00:18 -0500 [thread overview]
Message-ID: <878yeieyhp.fsf@trouble.defaultvalue.org> (raw)
Right now the srfi-4 code stores the length of uniform vectors in
SCM_CELL_WORD_2, and sometimes retrieves these lengths directly into
an int:
#define SCM_UVEC_LENGTH(u) (SCM_CELL_WORD_2(u))
...
int i = SCM_UVEC_LENGTH (uvec);
which is probably wrong for architectures where sizeof(int) <
sizeof(long), and in all cases, limits array sizes to 2GB. Other code
uses SCM_VALIDATE_INUM to check the lengths given to "make-FOOvector",
which limits the maximum array size even further.
So the thing I'm wondering about is how do we want our uniform vectors
to behave? Is it OK for their lengths to be limited to a fixnum?
What if someone wants to allocate a multi-GB s8 array on a 64-bit
machine, or a much smaller, but still larger than fixnum array on a
32-bit machine?
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-06-20 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 21:00 Rob Browning [this message]
2004-06-20 23:26 ` Uniform vector lengths -- how long? Kevin Ryde
2004-06-21 5:37 ` Rob Browning
2004-07-10 0:41 ` Kevin Ryde
2004-07-12 15:04 ` Rob Browning
2004-07-22 1:20 ` Kevin Ryde
2004-08-04 14:37 ` Rob Browning
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=878yeieyhp.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).