unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Roland Orre <roland.orre@neurologic.se>
Subject: 64bit guile: one bug found, one improvement suggested
Date: Wed, 27 Jul 2005 02:42:29 +0200	[thread overview]
Message-ID: <1122424950.8714.138.camel@bari.bacon.su.se> (raw)
In-Reply-To: <873bq1gn15.fsf@zagadka.de>

The (small) bug may be corrected in later version (I'm still
using the old style (early 1.7) uniform arrays). The improvement
suggested below is actually part of a general 32/64 bit problem.

bug:
size of scm_tc7_ivect and scm_tc7_uvect is long, but should be int.
causes: on 64 bit machine, there are no 32 bit int vectors available.
(I've fixed this locally)

improvement suggestion:
size of SCM should be configurable to 32 bit on 64 bit machine.
As it is now, it causes a lot of wasted memory and I guess also
unnecessary usage of memory band width.

This is a somewhat bigger change as most addressing needs to be
base relative. I guess there are utilites available to allocate
memory within certain (e.g. 32 bit) boundaries, (there was in VMS
I used once) but haven't found any in GNU/Linux, apart from
possibly start in mmap.
Maybe even gcc provides a nice solution to this, but haven't
found anything (someth like: short pointer and long pointer
which I think I've seen in some languages long time ago).

/Roland Orre




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


  reply	other threads:[~2005-07-27  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 23:33 The order of objects returned from a guardian Marius Vollmer
2005-07-27  0:42 ` Roland Orre [this message]
2005-07-28 22:37 ` Neil Jerram
2005-07-31 19:31   ` Marius Vollmer
2005-07-31 21:25     ` Marius Vollmer

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=1122424950.8714.138.camel@bari.bacon.su.se \
    --to=roland.orre@neurologic.se \
    /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).