Camm, it appears that the quadpack code has not changed, so if there's
any difference in Maxima, it would have to be outside of quadpack.
Maybe the default float type has changed from 64 bits to 80 bits or
vice versa? Only a guess; I don't know what else to suggest.
You could narrow the scope by
On Mon, Apr 8, 2024 at 8:36 AM Robert Dodier wrote:
> Running tests in rtestint:
> ** Problem 56 ***
> Input:
> cos(x)
> integrate(--, x, minf, inf)
>2
> x + 1
>
>
> Result:
>
, or in the assignments to those.
I would like to note that this bug is only observed with GCL 2.6.14.
Other Lisp implementations don't show it.
best
Robert
On Mon, Apr 8, 2024 at 8:36 AM Robert Dodier wrote:
>
> The current version of Maxima (00fcc04) bumps into several failures in
> rtes
The current version of Maxima (00fcc04) bumps into several failures in
rtestint when compiled with GCL 2.6.14.
GCL advertises itself as:
GCL (GNU Common Lisp) 2.6.14 Fri Jan 13 10:47:56 AM EST 2023 ANSIgit:
Version_2_6_14
The failures start with
Running tests in rtestint:
On Wed, Feb 28, 2024 at 7:40 AM Camm Maguire wrote:
> Does anyone care about anything other than 4 or 8 byte floats?
I know I don't, also I've never encountered, in 40+ years of numerical
programming, a problem that really needed bigger or smaller ones. I'm
not claiming those problems don't
Camm, thanks for taking the time to write about this stuff. I'm more
broadly interested in all of it, but in the interest of brevity I'll
just make a quick note.
It sounds like part of the proposal is to let program behavior change
with the compiler optimization setting. I'm pretty uncomfortable
On Thu, Dec 21, 2023 at 7:59 AM Camm Maguire wrote:
> Can you give me an example of something important
> which cannot be made to work with existing gcl characters, as say maxima
> has?
There isn't any feature in Maxima which requires Unicode, so unless
I'm forgetting something, the answer is
On Sun, Nov 5, 2023 at 7:06 AM Camm Maguire wrote:
> Greetings! Just to report that maxima's current use of $gensym (at
> least as of commit b6d66ad4e which is doubtless out of date by now)
> creates an implicit dependency on an unchanged *gensym-counter* binding,
> i.e. that the sequence of
On Mon, Jan 23, 2023 at 7:42 AM Camm Maguire wrote:
> Greetings! I see we've been on parallel paths.
>
> I've committed a lisp-array-alike1 to gcl_cleanup for review.
Well, commit a1de549 on master has special cases for strings and
vectors, and as it stands the problem with fill pointers has
On Tue, Nov 22, 2022 at 7:08 AM Camm Maguire wrote:
> Greetings, and thanks! Am I correct in assuming that 32bit builds are
> no longer useful?
I don't know to what extent people are using 32 bit systems. Maybe
someone else knows.
I don't know to what extent people who are creating packages
On Thu, Nov 10, 2022 at 5:25 AM James Cloos wrote:
> >>>>> "RD" == Robert Dodier writes:
>
> >> >(setq b (- a) c (- a a))
> >> #<-nan>
>
> RD> Minor wart here -- should be #, NaN doesn't have a sign.
>
> they do at the
On Tue, Nov 8, 2022 at 12:59 PM Camm Maguire wrote:
> The NaN report gives false now as you note,
> 2.0^1024.1 still gives the inf for testing purposes. I think the false
> is in simp-expt in maxima, but haven't got further. Most of his results
> had been fixed some time ago.
What? I don't
On Mon, Aug 29, 2022 at 9:56 PM Viktor T. Toth wrote:
> The offending line appears to be line #180 in build-html-index.lisp:
>
> (with-open-file (s "maxima-index-html.lisp"
>:direction :output
>:if-exists :supersede)
>
> which causes GCL to fail if the file
I've pushed commit eee5b4f to Maxima Git which changes the "//" in a
path to just "/", and now Maxima + GCL (Version_2_6_13pre120) can load
the package pslq successfully.
Hope this helps,
Robert
On Sun, Aug 7, 2022 at 3:18 PM Camm Maguire wrote:
> > Looks like the problem is that the construct path contains "//"
> > instead of just "/".
>
> This is true, gcl's parse-namestring cannot deal with the '//', which is
> not an ansi namestring to my understanding. Can you remove before
>
OK, great, I was able to successfully build pre120 on a gcc-4 system,
Maxima build is in progress, and it has gotten past the point where
pregexp.lisp is compiled, so I guess that's okay now.
The new executable identifies itself as "GCL (GNU Common Lisp) 2.6.12
ANSIFri Apr 22 15:51:11 UTC
I was able to successfully rebuild GCL (Version_2_6_13pre119) on a
system w/ GCC 9.
That GCL successfully compiles the current Git version of Maxima,
although it runs into a few errors in the main part of the test suite,
and then a large number of errors in the share tests. The share errors
seem
Camm, here's what I get when I run make in gcl-Version_2_6_13pre119/gcl.
uname -a reports:
Linux freekbox 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:23:46
UTC 2014 i686 i686 i686 GNU/Linux
gcc --version reports:
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
ld --version reports:
GNU ld (GNU
the numbers.
Maybe this provides some useful inspiration, I don't know.
best,
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/gcl-devel
the build machinery?
Is there a way to test for version 2.6.11+ ? Is it worth the trouble?
... I'm generally a little hesitant about including version tests.
best
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
https://lists.gnu.org/mailman
. Segfaults at the step where it tries to run
the raw GCL .exe file.
I'm giving up at this point. Maybe I'll try again in a few years,
or maybe someone else can sort it out.
Thanks for all your help -- it was fun.
best
Robert Dodier
___
Gcl-devel mailing list
/home/robert/tmp/gcl-git/gcl/gcl/unixport/msys does indeed exist and
if I enter that command line to bash, it apparently runs (and returns
immediately with exit code = 0).
Advice?
Thanks for your help,
Robert Dodier
___
Gcl-devel mailing list
Gcl
‘initlisp’:
main.c:753: error: ‘RTLD_LAZY’ undeclared (first use in this function)
main.c:753: error: ‘RTLD_GLOBAL’ undeclared (first use in this function)
make[1]: *** [main.o] Error 1
Suggestions?
best
Robert Dodier
___
Gcl-devel mailing list
Gcl
in README.wine but I run into this error:
$ ./configure --host=mingw32
[...]
checking for CFLAG -Wno-unused-but-set-variable... configure: error:
in `/home/robert/tmp/gcl-git/gcl/gcl':
configure: error: cannot run test program while cross compiling
??
best
Robert Dodier
On Thu, Oct 17, 2013 at 12:43 PM, Camm Maguire c...@maguirefamily.org wrote:
Greetings! git checkout Version_2_6_10pre ?
OK, tried that -- same error.
best
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
https://lists.gnu.org/mailman
/robert/tmp/gcl-git/gcl/gcl':
configure: error: cannot run test program while cross compiling
See `config.log' for more details
I've attached the file config.log too.
best
Robert Dodier
config.log
Description: Binary data
___
Gcl-devel mailing list
Gcl
-mparam.h files.
As for confdefs.h, I see it is in the top-level gcl directory,
so I wonder why it wasn't found.
Thanks for your help,
Robert Dodier
PS. I've also attached config.log.
config.log
Description: Binary data
___
Gcl-devel mailing list
Gcl
you can shed on this.
best
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/gcl-devel
, not just maxima.exe.
The GCL versions involved are 2.6.9 and 2.6.8 as of 2013-01-01.
Thanks for any light you can shed on this.
best
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/gcl-devel
don't remember for sure.
Thanks for working on GCL.
best
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
about the Debian build process, but for the record
it is not necessary to build the reference manual documentation since
the tarball contains the .info and .html generated from the .texi files.
HTH
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel
declaims.
All the best, keep up the good work.
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
On 3/5/07, Camm Maguire [EMAIL PROTECTED] wrote:
Greetings! I think this has been fixed in cvs head. Please let me
know if this is critical to you for 2.6.8.
Camm, thanks for taking a look at that. I don't think it is critical.
best
Robert Dodier
.
SBCL and Clisp both output an empty space for these.
Also, iirc the CLHS has examples which show empty spaces for these.
Maybe someone can look into this.
Thanks very much,
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
http
Camm, thanks for this information --
(in-package 'compiler)
;;WRITE-CHAR
(push '((t) t #.(flags set)
@0;(writec_stream(char_code(#0),sLAstandard_outputA-s.s_dbind),(#0)))
(get 'write-char 'inline-unsafe))
Trying various fixes to src/suprv1.lisp I find that the following is
enough to avoid
what might trigger the problem.
I can email the generated C code if anyone is interested.
Thanks for any light you can shed on this problem.
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
Forwarding this message from the Maxima mailing list.
Context: http://sourceforge.net/support/tracker.php?aid=1483203
Any comments would be much appreciated.
All the best, thanks for your help.
Robert Dodier
-- Forwarded message --
From: Vadim V. Zhytnikov [EMAIL PROTECTED
imply GCL 2.6.8 or later is required to compile Maxima
on all platforms. Since most people are using the precompiled
Windows package, I don't see a problem with that.
All that is easy for me to say, of course -- I don't have a Windows
build environment.
All the best
Robert Dodier
On 10/24/06, Vadim V. Zhytnikov [EMAIL PROTECTED] wrote:
I'm not sure this is really GCL bug. The point that gcl
always resets *tmp-dir* on start up. But this doesn't
happen with Maxima image. Probably Maxima itself should
take care of resetting *tmp-dir*.
Why is *tmp-dir* not assigned
in wrong places.
Thanks a lot for all your hard work!
Robert Dodier
___
Gcl-devel mailing list
Gcl-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
On 8/26/06, Vadim V. Zhytnikov [EMAIL PROTECTED] wrote:
Today I have tried gcl 2.6.8pre from CVS with
Maxima 5.9.3 and Maxima 5.9.3.99rc2 - build and
run_testsuite() are perfectly OK. And the most
important problem with gcl-xmaxima interaction
is gone.
Which problem was that?
best,
Robert
Hello,
I am working with GCL 2.6.7. It appears that the maximum number of
arguments is about 64. I wonder if there is a way to increase that,
either at run time or when GCL is built. Is there a way to specify
no fixed limit ?
Thanks for any information,
Robert Dodier
that
important -- probably a warm-start capability is more significant.
maybe you've already concluded the same yourself.
anyway, i mention this stuff just for the record.
thanks for your interest in this topic all the best,
robert dodier
___
Gcl-devel
to distinguish one NaN from another.
That said, I'd be happy enough if a NaN were printed as
NaN or NAN or some such when *PRINT-READABLY* is false,
and NAN-XXX or something (with X's representing
hex digits here) when it's true.
For what it's worth,
Robert Dodier
message about printing the result.
What needs to be modified in GCL in order to make
floating point inf and nan (not a number) printable?
Thanks for any insights.
Robert Dodier
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection
nan = t -- should be nil.
Also, I didn't try to exhaustively test all properties.
Thanks for your help,
Robert Dodier
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http
46 matches
Mail list logo
