't know what else to suggest.
>
> You could narrow the scope by tracing SLATEC::DQK31 and then only
> calling that function; maybe that helps a little.
>
> best,
>
> Robert
>
>
>
--
Camm Maguire
to anyone who is not
trying to ensure the GCL code is correct. I'll try for a bit longer to
see if I can flesh out any bugs and then just add an expected failure
where appropriate.
Take care,
Robert Dodier writes:
> On Sun, May 26, 2024 at 4:38 PM Camm Maguire wrote:
>
>> Greetings!
utput* *standard-output* )
>
> #
>
> MAXIMA> (my-error-fn "An error occurred.")
> An error occurred.
> T
>
>
> MAXIMA> (setf *error-output* (make-string-output-stream ))
>
> #
> MAXIMA> (my-error-fn "An error occurred.&q
Greetings! Has fricas removed axiom's )fin (restart) pair? How does
one escape to/from lisp at the fricas prompt?
Take care,
Camm Maguire writes:
> Greetings, and thanks so much for the suggestion!
>
> This works. I now have a 2.7.0 and fricas tree with minor modification
And the trap disabled until you reenable it thereafter.
> If I had selected option 2, would the traps be preserved?
Yes.
In the 2.6 series, you first have to (setq si::*print-nans* t) (which is
being eliminated), and you do not have the continue restart as an option.
Take care,
-
iler::nan 1.0)))
(# 1.0)
and return this when not trapping, but defining some additional cell
containing the NaN result for use in subsequent processing. The chief
argument against this appears to be performance.
Take care,
--
Camm Maguire
Greetings! Typo in my previous note:
Camm Maguire writes:
> the boolean test (e.g (if (car x) (listp x) t) -> t). There must be
should read
(e.g (if (consp x) (listp x) t) -> t)
(progn (car x) (listp x)) -> t at safety 0. But currently due to the
lack of reverse handling, (pr
nt exception trapping
2 Return to top level.
>>2
Top level.
>
=========
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
us, an 'assert' can be used as a *hint* to the compiler about
>
> how to handle the induction involved when inferencing processes a loop or a
>
> recursion.
>
>
>
> One overall goal of the compiler is to convert 'assert' predicates into
> compile
>
> time *con
loating-point-exceptions, then there is no error.)
>
> By the way, you asked, regarding other Lisps:
>
>> Can one access/manipulate nan at the lisp prompt level?
>
> See attached, which I think answers your question positively for
> LispWorks, Allegro CL, and CCL, but perhaps ne
) (has (Integer)
(RetractableTo (Fraction (Integer)
I'm digging into this and will find it eventually, but if you have any
debugging suggestions I'm sure that would speed things up.
Take are,
Waldek Hebisch writes:
> On Sat, Mar 02, 2024 at 08:56:14AM -0500, Camm Maguire wrote:
>> Gree
look in the boot parser source to suggest a patch
breaking this into an nconc of several compliant list calls, or better
yet just writing a quoted list (since apparently all contents are
strings) which the reader can handle just fine?
Take care,
--
Camm Maguire
bignum 'registers' which we do not expose to lisp, as if they
contain fixnums the logic pertaining to the same will fail. I suppose
an expert user could make use of the registers and be careful not to
refer to them until the gmp calculation is done.
Take care,
> RJF
>
> On Wed, Feb 28, 2
ke three arguments,
overwrite the first, and return no values. Your thoughts?
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
single-float
> most-positive-double-float most-positive-long-float)
(3.4028235e38 3.4028235e38 1.7976931348623157d308 1.189731495357231765l4932)
Take care,
--
Camm Maguirec...@ma
mplex is a valid type, at least
to gcc. Will try to investigate clang.
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
Greetings!
Raymond Toy writes:
> On Mon, Feb 26, 2024 at 5:28 AM Camm Maguire wrote:
>
> Greetings, and thanks to all for the very helpful feedback!
>
> I'd also like to note in passing that the excellent SBCL out of the box
> triggers an error, which we separately refer t
10) (exp 10))
T
COMPILER>(= (exp 10) (exp 10))
T
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
s so bad. I don't see how we can reason
about real numbers without relying on their constituting a field.
I'd be particularly interested in your opinion on the two alternatives I
set out in separate email, given how I've based GCL's type system on
your paper :-)
Take care,
--
Camm Maguire
gt; you are ok. Other examples, probably not.
> Consider (cos NaN). Returning NaN is one option. How about returning
> an interval [-1,1]?
> {one way of implementing intervals may be to encode them ... e.g. NaN
> payload is
> a pointer to a hashtable entry. The entry is lower/upper
ical values should not trigger an
error when passed a symbol as argument, presuming that some of the
returned values might still be correctly computed?
To my mind, type checking on arguments is done at the top of a
function. If compiling without safety, the type checks can be dropped.
e how other lisps handle
this? Can one access/manipulate nan at the lisp prompt level?
Take care,
> Take care,
> --
> Camm Maguirec...@maguirefamily.org
> ======
Greetings!
x86_64 please. Did not know macos had arm64, but we can deal with that
later
Take care,
Kirill A. Korinsky writes:
> On Tue, 20 Feb 2024 20:11:31 +0100,
> Camm Maguire wrote:
>>
>> Thanks so much! No rush at all. SSH key sent in separate email.
>&
but
the user could still access the values when compiling at (safety 0).
Thoughts?
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and man
Thanks so much! No rush at all. SSH key sent in separate email.
Take care,
Kirill A. Korinsky writes:
> On Tue, 20 Feb 2024 01:19:03 +0100,
> Camm Maguire wrote:
>>
>> I do think the Sonoma access is probably the most efficient way to go
>> from here.
>>
>
r proposed code changes! (I think this
> means the crashing is sensitive to particular memory layout, or due to
> memory leaking, thus not always reproducible.)
>
> Hope this helps...
>
> P.S. I think I can provide you a remote access to a mac
efore passing to
the C compiler.
> 2. Under C++ environment assumptions, the prototype declarations without
> arguments have been wrongly treated as different (C++) functions.
>
This may be the case. What I suspect is that linking a -no-pie raw
executable might imply some different standard
; P.S. My Apple hardware is a bit wired. On Catalina or even Snow Leopard
> (10.6), GCL 2.6.14 is already available from MacPorts. But if I try to
> build the GCL package locally in my machine, I think the same crashing
> will happen - and my two MacBook Pro (both are 2019 Intel chips but
>
envp=0x7ff7bfefee68) at main.c:633:21
>> frame #3: 0x7ff811831386 dyld`start + 1942
>> (lldb)
>
> What does "flat namespace" mean? Is GCL's C code being (wrongly)
> considered/handle as C++ code and is somehow miscompiled due to the new
> C++ standa
t; c_apply_n(f=, n=1, x=) at apply_n.h:6:19 [opt]
>> >> frame #74: 0x000100056f80
>> raw_pre_gcl`quick_call_function_vec_coerce [inlined]
>> c_apply_n_fun(fun=, n=, b=)
>> at apply_n.h:79:38 [opt]
>> >> frame #75: 0x0001
00056f80 raw_pre_gcl`quick_call_function_vec_coerce
>> [inlined] c_apply_n_fun(fun=, n=, b=)
>> at apply_n.h:79:38 [opt]
>> frame #84: 0x000100056f71 raw_pre_gcl`quick_call_function_vec_coerce
>> [inlined] quick_call_function_vec(fun=, n=,
>> b=) at eval.c:7
$3;i=1}' |
> tr -d '"'
> /opt/local/include/gmp.h
>
> Therefore, I think you should at least put $CFLAGS inside the above
> configure.in code pieces, to handle non-standard position of GMP headers
> given by CFLAGS.
>
> P.S. in you macOS Catalina environment, if you h
, in the function, many other Lisp functions are
>> referenced, but these functions are to be defined at later position of
>> the code, and thus their type information is unknown. GCL 2.6.x can
>> compile this file any way, but the current GCL 2.7.0 compiler seems
>> failing in
sed on GCC 13.)
>
Good to hear. I had trouble with gcc13 on Catalina which I did not
pursue as it would not get me gprof anyway :-(. I'm using the external
gmp library which works well -- does this not work for you? I'm
thinking of removing the convenience copy of gmp4.
Take care,
--
C
system "out")).
>
> 4. Can you do a review of the various "#+:GCL" to see if they are still
> needed after gcl-2.6.14?
Yes, will do, as well as commit the items (all gcl specific) I alluded
to in a previous email.
Take care,
>
iterate on conflict,
and I think this is too slow. Pointers most appreciated!
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankin
file.
The older mechanism will continue to be supported. Is this something
that might be used in fricas?
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is bu
E=0.1
for example limits the process to 1/10 available memory. This should be
unnecessary, so please report where it is necessary so I might fix it.
Take care,
--
Camm Maguirec...@maguirefamily.org
Greetings! When running under lldb, running any subprocess via
posix_spawn fails at waitpid with errno set to 'interrupted system
call'. I suppose I could try blocking things, but suggestions?
Take care,
--
Camm Maguirec...@maguirefamily.org
been discussed in the
mailing list before.
Take care,
>
> Regards,
> - Greg
>
>
>
>
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
re".
>
> P.S. Very glad to hear the good news ("macports success")! I hope soon
> the prebuilt GCL 2.7.0 binaries will be available to all MacPorts users
> on various (recent) versions of macOS. (And I will use your debian
> patches to build Axiom with external GCL.)
>
>
"Software Update"?
-lgcrt1.o (gprof, -pg) is missing from the MacPorts gcc13 package -- is it
anywhere
else?
Take care,
> [1] https://xcodereleases.com
>
> Chun
>
> On 31/01/24 06:19, Kirill A. Korinsky wrote:
>> Greetings,
>>
>> On Tue, 30 Jan 202
s! Let me reproduce your success on macOS 12 first. (I'm not
>> very useful here except that I can be a good manual tester.)
>>
>
> I'd like to point that current master doesn't build.
>
> I had build it last time in middle of December with some ugly hacks.
-
Greetings! Also, is there anything I can do to shorten the
pathnames/filenames in the macports builds?
Take care,
Kirill A. Korinsky writes:
> Greetings,
>
> On Tue, 30 Jan 2024 17:28:11 +0100,
> Camm Maguire wrote:
>>
>> I have an old mac virtualbox which I never use
Greetings, and thanks for these instructions. Making progress here, but
Kirill A. Korinsky writes:
> The simplest way to update it is:
> 1. Update git commit
I have no command 'Update', typo?
Take care,
--
Camm Maguirec...@maguirefami
17:28:11 +0100,
> Camm Maguire wrote:
>>
>> I have an old mac virtualbox which I never use except at the last point
>> in gcl releases. Nonetheless I have fired it up, and run into the
>> problem that sed cannot put newlines into the replacement text. You
>> guy
m
>>> using Intel mac).
>>>
>>> I think it's OK to ignore macOS versions where readlinkat() is not
>>> available, because on those old platforms GCL 2.6.12 at least works.
>>>
>>> P. S. Once GCL 2.7 is working, I'll try my best to get AXIOM working
old platforms GCL 2.6.12 at least works.
>
> P. S. Once GCL 2.7 is working, I'll try my best to get AXIOM working
> with it.
>
> --Chun
>
> On 30/01/24 01:51, Camm Maguire wrote:
>> Greetings! Found it, thanks so much! You should be good to go now on
>> master. Plea
g Intel mac).
>
> I think it's OK to ignore macOS versions where readlinkat() is not
> available, because on those old platforms GCL 2.6.12 at least works.
>
> P. S. Once GCL 2.7 is working, I'll try my best to get AXIOM working
> with it.
>
> --Chun
>
> On 30/01/24 01:51,
Greetings! Unexpected. At this point please do
cd unixport
make raw_gcl_gcl
gdb raw_pcl_gcl
(gdb) r ./ writes:
> On Mon, 29 Jan 2024 15:51:57 +0100,
> Camm Maguire wrote:
>>
>> Greetings! Found it, thanks so much! You should be good to go now on
>> master. Please
Greetings! Found it, thanks so much! You should be good to go now on
master. Please let me know if problems persist.
Take care,
Kirill A. Korinsky writes:
> On Mon, 29 Jan 2024 04:37:55 +0100,
> Camm Maguire wrote:
>>
>> But configure did not detect it in your problem bui
Greetings! OK then please repeat the last instructions, inserting the
following before (load "boot.lisp")
>(trace si::readlinkat)
Take care,
Kirill A. Korinsky writes:
> On Mon, 29 Jan 2024 04:37:55 +0100,
> Camm Maguire wrote:
>>
>> But configure did not
Greetings!
But configure did not detect it in your problem build?
Take care,
Kirill A. Korinsky writes:
> On Mon, 29 Jan 2024 00:20:43 +0100,
> Camm Maguire wrote:
>>
>> Greetings, and thanks so much! Its the readlinkat we commented out on
>> mac -- we need a r
Greetings, and thanks so much! Its the readlinkat we commented out on
mac -- we need a replacement. Suggestions?
Take care,
Kirill A. Korinsky writes:
> Greetings,
>
> On Sun, 28 Jan 2024 16:45:59 +0100,
> Camm Maguire wrote:
>>
>> Greetings, and thanks again
nued: Repeat assertion.The assertion (APPLY (QUOTE ARRAY-IN-BOUNDS-P)
> ARRAY ...) failed.
>
> Broken at LET*. Type :H for Help.
> 1 (continue) Repeat assertion.
> 2 Return to top level.
> COMPILER>>make: *** [unixport/saved_gcl0
))
>
> Correctable error: The assertion (APPLY (QUOTE ARRAY-IN-BOUNDS-P) ARRAY ...)
> failed.
> Signalled by APPLY.
> If continued: Repeat assertion.
> The assertion (APPLY (QUOTE ARRAY-IN-BOUNDS-P) ARRAY ...) failed.
>
> Broken at LET*. Type :H for Help.
> 1 (continue) Re
error: frame stack overflow.
> Emergency reset complete
>
> on raw_pre_gcl < foo
>
> :(
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
mp; interrupt_enable )
> 688 {catch_fatal = -1;
> 689 #ifdef SGC
> 690 if (sgc_enabled)
> Target 0: (raw_pre_gcl) stopped.
>
> but any attempt to use bt leads to 100% CPU usage by LLDB.
>
> All of this indicates that something quite bad with memory when this ENV is
> enabled.
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
mp;
o->sm.sm_fp!=stdin && o->sm.sm_fp!=stdout && o->sm.sm_fp!=stderr) {
+ printf("Closing %p, %p %p %p %p %p
%p\n",o->sm.sm_fp,stdin,__stdinp,stdout,__stdoutp,stderr,__stderrp);
+ fflush(stdout);
close_stream(
?
>
> _______
> Maxima-discuss mailing list
> maxima-disc...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/maxima-discuss
>
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
image();
>
> so, regarding naming. It is defined as
>
> #define stdin __stdinp
> #define stdout __stdoutp
> #define stderr __stderrp
>
> See:
> https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX11.3.sdk/usr/incl
_zone->memalign = (void *) stub_memalign;
#endif
for (i=0;i writes:
> Hello,
>
> On 24. Dec 2023, at 15:34, Camm Maguire wrote:
>
> Please export the environment variable GCL_MEM_MULTIPLE=0.1 or similar
> to limit gcl to 1/10 of system memory. There are also ways to do
irill A. Korinsky" writes:
> Hello,
>
> On 24. Dec 2023, at 15:55, Camm Maguire wrote:
>
> BTW the memory consumption issues should be identical to 2.6. Please
> let me know if your mileage varies.
>
> 2.6.14 builds on the same machine via same MacPorts with near the
it is quite different:
> -
> https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX11.3.sdk/usr/include/mach-o/x86_64/reloc.h
> -
> https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX11.3.sdk/usr/include/mach-o/arm64/reloc.h
--
Camm Maguire
Greetings! OK, thanks for the clarification
"Kirill A. Korinsky" writes:
> Hello,
>
>> On 24. Dec 2023, at 15:37, Camm Maguire wrote:
>>
>>>
>>> Anyway, failed on build; crash happened inside siLheap_report which is
>>> called by the f
ARRAY ...)
> failed.
> Signalled by APPLY.
> If continued: Repeat assertion.The assertion (APPLY (QUOTE
> ARRAY-IN-BOUNDS-P) ARRAY ...) failed.
>
> Broken at LET*. Type :H for Help.
> 1 (continue) Repeat assertion.
> 2 Return to top level.
> COMPILER>
Greetings!
>
> Anyway, failed on build; crash happened inside siLheap_report which is called
> by the first (init-system) at ./raw_pre_gcl
Is this heap report issue the same as your segmentation catcher signal
unblocking issue and limited to arm64 alone?
Take care,
--
Cam
1 (continue) Repeat assertion.
> 2 Return to top level.
> COMPILER>>make: *** [unixport/saved_gcl0] Error 255
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
y, regarding your previous comments on large memory
consumption. Please export GCL_MEM_MULTIPLE=0.1 or similar to limit gcl
to 1/10 of system memory. There are also ways to do this at the lisp
level.
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
/* unblock_signals(SIGSEGV,SIGSEGV); */
> +/* unblock_signals(SIGBUS,SIGBUS); */
> +/* (void) gcl_signal(SIGSEGV,segmentation_catcher); */
> +/* (void) gcl_signal(SIGBUS,segmentation_catcher); */
> }
>
A new issue specific to arm? Where does it fail without this?
Take care,
--
Camm
opt/local/var/macports/build/_Volumes_SharedFolders_Home_src_macports-ports_lang_gcl/gcl-devel/work/33a195d5cec2a7f8f563e11c0f1a3011ea0b30a0/gcl/
> < foo
> make[1]: *** [saved_pre_gcl] Error 132
>
> which probably th
; 5
> 6
> 7
> 8
> zsh: illegal hardware instruction ./raw_pre_gcl
> catap@Kirills-mini-m1 unixport %
>
> So, it seems clear which line triggers an issue O:-)
>
> Thus, I've changed the problem line to
>
> printf("8\n");fflush(stdout);
> make_fixnum(((unsigned long)cs_base+i-1)&-i);
> printf("9\n");fflush(stdout);
>
> and it crashes the same way.
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
b.lsp
> zsh: illegal hardware instruction ./raw_pre_gcl ./
> catap@Kirills-mini-m1 unixport %
>
> thus, meanwhile I made some investigation and localized the crash exact line
> in siLheap_report function:
> vs_push(make_fixnum(((unsigned long)cs_base+i-1)&-i));
>
>
try
> (load (compile-file "../lsp/gcl_fpe_test.lsp"))
Take care,
"Kirill A. Korinsky" writes:
> i386
>
> 1. it has missed AC_CHECK_SIZEOF(char,0) in configure.in
>
> 2. it has missed FPE_RLST for the case non x86_64, see config.h
ff
>
> Crashes attached as gcl.txt and gcl-devel.txt
>
> It crashes the same way on arm64 when I use rosetta to emulate x86_64 and on
> native x86_64.
>
> To make things easy I've attached all used patches / stacktrace to thi
EDITLINE :TRUNCATE_USE_C :CLX-LITTLE-ENDIAN :BSD
> :DARWIN21.6.0 :X86_64 :IEEE-FLOATING-POINT :DARWIN :UNIX :GMP :GCL
> :AKCL :COMMON :KCL)
>
> COMPILER>
> #<"SYSTEM" package>
>
> SYSTEM>
> T
>
> SYSTEM>
>
> and it
/* errno=0; */
+ /* execvp(*p1,(void *)p1); */
+ /* _exit(128|(errno&0x7f)); */
+ /* } */
massert(pid>0);
massert(pid==waitpid(pid,,0));
Take care,
--
Camm Maguirec..
which will hopefully get you beyond the libc
issue. Please keep me informed.
Take care,
"Kirill A. Korinsky" writes:
> On 22. Dec 2023, at 17:19, Camm Maguire wrote:
>
> On 3), after reading up on vfork, and examining your logs, it is indeed
> deprecated. This
To all: gcl27 packages are now in the debian new queue. For those with a debian
unstable environment around, .deb files can be downloaded from
http://people.debian.org/~camm
Take care,
--
Camm Maguirec...@maguirefamily.org
38.6M 42
> __DATA_CONST 352K 37
> __DATA_DIRTY58K 22
> __HEAP 32.0G 24
> __LINKEDIT
l/configure.in
> @@ -385,7 +385,7 @@ fi
> AC_SUBST(GCL_CC)
>
>
> -GPROF="gprof_objs"
> +GPROF="gprof"
> AC_ARG_ENABLE([gprof],[ --enable-gprof builds gcl with -pg in CFLAGS to
> enable profiling with gprof],
> [if test "$enablev
fatal error [memory may be damaged]: Segmentation
> violation."
> Signalled by MULTIPLE-VALUE-BIND.
> Segmentation violation: c stack ok:signalling errorERROR "Caught fatal error
> [memory may be damaged]: Segmentation violation."
>
> Broken at LET*. Type :H for Help.
> 1 Return to top level.
> COMPILER>>make: *** [unixport/saved_gcl0] Error 255
> rm h/mcompdefs.h
>
> and without the first one, if I recall right, it's failed near the similar
> way but at the end, when it saves the image.
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
er it is safe to define __EXTENSIONS__... yes
> checking whether _XOPEN_SOURCE should be defined... no
> ./configure: line 4095: #include: command not found
> checking for gawk... no
> checking for nawk... nawk
>
> No error, but not buildable.
>
> - Greg
>
>
>
>
_CFLAGS
> + AC_DEFINE(USE_GPROF,1,[use gprof])
> fi
> fi
> AC_SUBST(GPROF)
> diff --git a/gcl/o/main.c b/gcl/o/main.c
> index ae93a228f..ba945bee0 100644
> --- a/gcl/o/main.c
> +++ b/gcl/o/main.c
> @@ -370,7 +370,9 @@ minimize_image(void) {
>nrbpage
Greetings!
Some time ago I put in the gobble-whitespace function for gcl (commit
da00ca3cf) to work around test failures linked to unicode whitespace.
Workign fine AFAICT.
Take care,
Robert Dodier writes:
> On Thu, Dec 21, 2023 at 7:59 AM Camm Maguire wrote:
>
>> Can you give m
ine VM1 0
static void * VVi[2]={
#define Cdata VV[1]
(void *)(LI1__CMP_ANON___gazonk_729566_0)
};
#define VV (VVi)
NIL
COMPILER>
=====
Take care,
--
Camm Maguire
care,
"Andrey G. Grozin" writes:
> Camm,
>
> Will 2.7.0 support unicode?
>
> Andrey
>
>
>
--
Camm Maguirec...@maguirefamily.org
==
"The ea
macports-ports/blob/master/lang/gcl/files/dont-override-CC-or-MACOSX_DEPLOYMENT_TARGET.patch
> -
> https://github.com/macports/macports-ports/blob/master/lang/gcl/files/fix-memory-corruption-on-macOS.patch
> -
> https://github.com/macports/macports-ports/blob/master/lang/gcl/files/old-
t of ASDF out of the box?
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
try to boil these
down to the lisp level. I have not yet tried building the standard
programs with this version on a production basis, but will ensure that
all are supported at existing performane or better before making a
standard release.
Take care,
--
Camm Maguire
Greetings!
Robert Dodier writes:
> On Sun, Nov 5, 2023 at 7:06 AM Camm Maguire wrote:
>
> What is the test case which shows Maxima gensym not working correctly?
> Maybe it's serious enough after all.
>
Having spent some time to see if I could cache gensyms in setf
expansions
.
This is obviously not too important, and gcl will make sure to stay
clear of this for maxima's sake.
Take care,
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one co
arg.
>
> How do I invoke enough-namestring to produce what I want, like other lisps do?
>
>
>
--
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
have been agreed upon.
>
>
>
> primep(n), next_prime(n), inverse_mod(m,n), jacobi(m,n), legendre(a,p),
>
> kronecker(a,b), factorial(n), binomial(n,k), fibonacci(n), lucas(n), etc.
>
> But getting lisps to support this is probably eas
Peetz writes:
> Package: maxima
> Version: 5.46.0-11
> Severity: normal
>
> Dear Camm Maguire,
>
> calling maxima generates a kernel message:
>
> kernel: __vm_enough_memory: 1 callbacks suppressed
> kernel: __vm_enough_memory: pid: 13721, comm: maxima, no enou
if any this incurs.
Take care,
Camm Maguire writes:
> Greetings! Doubtless there are many lisp-oriented optimizations
> possible with the instruction set. GCL, once ported, of course will
> still go through gcc, so the assembler will by default be somewhat
> 'generic'. GCL can ha
Greetings! This seems to work, but not I'm getting "Cannot connect to
FRICAS server" in sman during the doc build stage. Any suggestions?
Take care,
Camm Maguire writes:
> Greetings!
>
> Think I've spotted this:
>
> daase.lisp:
>
> ; #-:GCL
> (
system-p* t)' \
> + ' (setq compiler::*default-large-memory-model-p* t))"' \
>' si::*system-directory* (quote (list ".lsp")))' \
> ' "$(lisp_c_objects) $(fricas_c_runtime_extra)")' \
> | $
Greetings!
Waldek Hebisch writes:
> On Fri, Feb 10, 2023 at 09:11:41AM -0500, Camm Maguire wrote:
>> Greetings!
>>
>> Might I please be granted git access to maintain the gcl/fricas
>> interface?
>>
>
> Of course. What is your Github id?
>
>
> Handy for scripts that want or need to know the version.
>
> More convenient than having to figure out how to use -eval and friends to
> print it out, and so many gnu programs already support --version.
--
Camm Maguire
1 - 100 of 1276 matches
Mail list logo
