GNU bug report logs - #11087
vector limitation in compiling to bytecode

Previous Next

Package: guile;

Reported by: Ian Price <ianprice90 <at> googlemail.com>

Date: Sat, 24 Mar 2012 20:42:02 UTC

Severity: normal

Done: Andy Wingo <wingo <at> pobox.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ian Price <ianprice90 <at> googlemail.com>
To: 11087 <at> debbugs.gnu.org
Cc: wingo <at> pobox.com
Subject: bug#11087: vector limitation in compiling to bytecode
Date: Fri, 06 Jul 2012 07:52:15 +0100
Andy Wingo <wingo <at> pobox.com> writes:

> On Sat 24 Mar 2012 21:09, Ian Price <ianprice90 <at> googlemail.com> writes:
>
>> ;;; ERROR: In procedure bytevector-u8-set!: Value out of range: 390
>> vector constant containing 100000 values
>>
>> This limitation is documented, and somewhat reasonable, but on IRC mark
>> weaver asked me to file a bug anyway, since he thinks the assembler
>> should have a fall back plan.
>
> I agree with Mark.
>
> For what it's worth, if the vector is really constant (e.g. just
> composed of immediates), the RTL VM will emit the whole thing
> statically.  Otherwise it will emit code to allocate a vector
> of the right size at init time, initializing its elements with
> individual instructions.   This latter strategy is probably the right
> thing to do with the Guile 2.0 VM.
In my case, it was completely static. I had generated the vector from
another file, of existing data. It's good to hear this will work in the
future rtl based guile.

Thanks

-- 
Ian Price

"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"




This bug report was last modified 12 years and 324 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.