Hi Alex,
interesting. Thanks for explanation.
Tomas
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Alex,
> No, it is a different symbol, defined in the 'llvm' namespace (see my
previous
> mail).
Ok got it, thanks!
BR,
Geo
On Mon, Apr 13, 2020 at 4:55 PM Alexander Burger
wrote:
> Hi Geo,
>
> > Would that be the 'car' from the running pil64?
>
> No, it is a different symbol, defined in
Hi Geo,
> Would that be the 'car' from the running pil64?
No, it is a different symbol, defined in the 'llvm' namespace (see my previous
mail).
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Tomas,
> ># (car 'var) -> any
> >(de _car (Exe)
> > (car (needVar Exe (eval (cadr Exe )
>
> ^
> what is this car?
It is a function defined in "src/lib/llvm.l":
(asm ()
((X)
(ssa (inc '*Ssa) "inttoptr i64 " X " to i64*")
(ssa (inc '*Ssa) "
Would that be the 'car' from the running pil64?
BR,
Geo
On Mon, Apr 13, 2020 at 3:55 PM Tomas Hlavaty wrote:
> Hi Alex,
>
> interesting.
>
> Alexander Burger writes:
> > Now in pil21 the source is (in "src/subr.l"):
> >
> ># (car 'var) -> any
> >(de _car (Exe)
> > (car (needVar
Hi Alex,
interesting.
Alexander Burger writes:
> Now in pil21 the source is (in "src/subr.l"):
>
># (car 'var) -> any
>(de _car (Exe)
> (car (needVar Exe (eval (cadr Exe )
^
what is this car?
Tomas
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Alex!
You might perhaps have noticed, that modern CPUs execute "unoptimized"
compiler code almost as fast as code produced by highly optimizing
compilers (-Os vs. -O3). Difference is almost zero!
You also might have noticed, that AMD with EPYC Rome and Threadripper are
far ahead of Intel in te
Happy Easter, Alex!
Nothing brings me to waste just a second on LLVM compiler suite. And i
directly will tell you why:
https://bellard.org/otcc/
OTCC is a C compiler implemented in 2048 bytes of code. It can compile
itself and translates to 386 machine code. Fully 'Turing complete'! Its
successo
On Sun, Apr 12, 2020 at 08:09:46AM +0200, Tomas Hlavaty wrote:
> Rowan Thorpe writes:
> > parentheses are not used because as is stated at
> > https://picolisp.com/wiki/?src64 "Assembly language is not a
> > functional language, i.e. the individual instructions do not "return"
> > a value. So a fu
t the PicoLisp philosophy of purity and
minimalism, it makes PicoLisp sources look a lot like Emacs Lisp
sources, but sometimes I want a nested structure when a file gets big,
and I might need more comments than the usual one-liner.
The trick is to enable outline-minor-mode in the .l source fil
10 matches
Mail list logo
