> On Apr 22, 2020, at 14:00, Alexander Burger wrote:
>
> Hi all,
>
> yesterday the Oktoberfest, the largest annual event in Bavaria, was canceled.
>
> I think we will also have to cancel the other large event, PilCon. It is not
> sure whether such events will be allowed legally by end of
> On Apr 22, 2020, at 14:00, Alexander Burger wrote:
>
> Would it make sense to plan an online conference instead? We are playing
> around
> with Jitsi Meet currently. Any thoughts?
You must be aware that the FSF's LibrePlanet was moved from IRL to Jisti (and
others) in just a few days of
Thanks Alex,
I was thinking of increased memory space - not exactly doubling - I was
thinking it would just be one additional byte per CELL. Ofcourse this
additional byte would not have the same lifetime of the CELL so it should
not need any extra management.
I feel encouraged - I'll give it a
Hi Kashyap,
> About the the CELL having an additional byte, I meant that the CELL size
> would be 2*WORD + 1... that should work too right? I would not need any
> masking in that case.
I see. Yes, that would work. But it would either double the memory usage, or
require some management of this
Hi all,
yesterday the Oktoberfest, the largest annual event in Bavaria, was canceled.
I think we will also have to cancel the other large event, PilCon. It is not
sure whether such events will be allowed legally by end of July, and how the
international travel situation will be.
I hope this is
Thanks Alex,
Yup, I can see what's going on now about RAM vs ROM :)
About the the CELL having an additional byte, I meant that the CELL size
would be 2*WORD + 1... that should work too right? I would not need any
masking in that case.
Regards,
Kashyap
On Mon, Apr 20, 2020 at 11:06 PM Alexander
Interesting. You might have also run into no "excution bits" on Intel
hardware:
https://releases.llvm.org/8.0.1/docs/SpeculativeLoadHardening.html
https://en.wikipedia.org/wiki/NX_bit
In Lisp, "code is data, data is code". There simply is no separation the
like - "code here, data there".
> Maybe not related to this one, but on Mac OS X the heap size is limited
> to 65532KB. On startup picolisp fails to set the unlimited stack size,
> And use the actual ulimit so on the first run I’ve got a SIGSEGV running
> code2015.l
>
Indeed! I always forget this requirement on Openbsd.
$
Hi Guido,
I am very interested to hear about your ASIC Lispm, how can we avail once
its out? Can you please share more details? Actually I am also trying to
get back from what we have started using FPGA but time is always not on my
side these days, but will see..
I really hope to hear from you
Hi,
Maybe not related to this one, but on Mac OS X the heap size is limited
to 65532KB. On startup picolisp fails to set the unlimited stack size,
And use the actual ulimit so on the first run I’ve got a SIGSEGV running
code2015.l
Andras
> On 2020. Apr 21., at 10:38, Mike wrote:
>
> hi all,
hi all,
> If you are interested I have patched the 19.12 32bit sources to compile
> without GCC.
> I have attached the changed files: pico.h, main.c, apply.c and flow.c
>
> Since clang does not support variable length array in structures I allocate
> the bindFrame
> with alloca() and provided
Hi Alex!
Webassembly already is ported to almost all architectures, where browsers
are available. All those Webassembly containers in those browsers takes
Binary Lisp code and do translate it to native machine code.
If you would please have a look at that giant list of programming
languages,
Hi Kashyap!
Dividing up Lisp Cells (Atoms) in RAM/ROM - i think, you're referring to
this: https://picolisp.com/wiki/-A265.html has recently got another aspect:
https://en.wikipedia.org/wiki/Remote_direct_memory_access
RDMA, Remote Direct Memory Access.
With Picolisp and especially miniPicoLisp
Hi Kashyap,
> 1. About RAM vs ROM. Call me lazy but I would really appreciate a
> description of how the RAM vs ROM decision is taken here (and in general
> too..I mean, it is not clear to me how gen3m.c determines how something is
> never written to or not)
> if (x > 0)
>
14 matches
Mail list logo
