- cmucl-imp - mailman3.common-lisp.net

[cmucl-imp] Fwd: [cmucl-help] NaN
by Raymond Toy 10 Jan '17

10 Jan '17

Oops. Meant to reply to all. ---------- Forwarded message ---------- From: Raymond Toy <toy.raymond(a)gmail.com> Date: Sun, Jan 8, 2017 at 10:00 AM Subject: Re: [cmucl-help] NaN To: Marco Antoniotti <marcoxa(a)cs.nyu.edu> On Sat, Jan 7, 2017 at 3:44 PM, Marco Antoniotti <marcoxa(a)cs.nyu.edu> wrote: > Hi > > I am fiddling around with some IEEE floating points. > > I see that the following code produces a (almost nice) “quiet” NaN. > > CL-USER> (ext:with-float-traps-masked (:invalid) > (* 0.0 ext:double-float-positive-infinity)) > #<DOUBLE-FLOAT Quiet NaN> > > Alas, there seem to be no way to tell the compiler that we are actually > executing the multiplication within the ext:with-float-traps-masked. This > prevents us, for example to do things like > > (defparameter NAN (ext:with-float-traps-masked (:invalid) > (* 0.0 ext:double-float-positive-infinity)) > > in a file and having it compiled “nicely”. The compiler complains (warns) > about a FLOATING-POINT-INVALID-OPERATION > > ; In: DEFPARAMETER NAN > > ; (* 0.0 EXTENSIONS:DOUBLE-FLOAT-POSITIVE-INFINITY) > ; Warning: Lisp error during constant folding: > ; Arithmetic error FLOATING-POINT-INVALID-OPERATION signalled. > ; Operation was *, operands (0.0d0 #.EXT:DOUBLE-FLOAT-POSITIVE-INFINITY). > What version? I don't get any warnings from snapshot-2017-01. > > Note that the value is then assigned correctly, but it seems very hard (at > least I did not figure out how to do it) to get to the constant folding > time to catch and muffle the warning. > > Any ideas? > Since you're using cmucl-specific functions, you could always just construct the NaN directly using kernel:make-double-float. Something like (kernel:make-double-float -524288 0) -- Ray -- Ray

3 8

[cmucl-imp] NaN
by Marco Antoniotti 07 Jan '17

07 Jan '17

Hi I am fiddling around with some IEEE floating points. I see that the following code produces a (almost nice) “quiet” NaN. CL-USER> (ext:with-float-traps-masked (:invalid) (* 0.0 ext:double-float-positive-infinity)) #<DOUBLE-FLOAT Quiet NaN> Alas, there seem to be no way to tell the compiler that we are actually executing the multiplication within the ext:with-float-traps-masked. This prevents us, for example to do things like (defparameter NAN (ext:with-float-traps-masked (:invalid) (* 0.0 ext:double-float-positive-infinity)) in a file and having it compiled “nicely”. The compiler complains (warns) about a FLOATING-POINT-INVALID-OPERATION ; In: DEFPARAMETER NAN ; (* 0.0 EXTENSIONS:DOUBLE-FLOAT-POSITIVE-INFINITY) ; Warning: Lisp error during constant folding: ; Arithmetic error FLOATING-POINT-INVALID-OPERATION signalled. ; Operation was *, operands (0.0d0 #.EXT:DOUBLE-FLOAT-POSITIVE-INFINITY). Note that the value is then assigned correctly, but it seems very hard (at least I did not figure out how to do it) to get to the constant folding time to catch and muffle the warning. Any ideas? Apart from that, what would take to have a “NaN” object available all the time? In LW and CCL you have the special syntax and object 1D+-0 For NaN Cheers -- Marco Antoniotti

1 0

[cmucl-imp] Snapshot 2017-01
by Raymond Toy 07 Jan '17

07 Jan '17

The new year brings us another CMUCL snapshot. Binaries will be uploaded soon. See the release notes for the changes, but here's a quick summary: * Ticket #34 fixed: Sparc build fails test issues-tests::issue.25a * Ticket #38 fixed: Don't use unix:unix-times * bin/make-dist.sh options have changed. The positional args for the version, architecture, and os are removed in favor of switches -V, -A, and -o, respectively.

1 0

[cmucl-imp] [CfP] ELS'17, 10th European Lisp Symposium, April 3-4 2017, Brussels
by Didier Verna 03 Jan '17

03 Jan '17

ELS'17 - 10th European Lisp Symposium VUB - Vrije Universiteit Brussel Belgium April 3-4, 2017 In co-location with <Programming> 2017 Sponsored by Brunner Software GmbH http://www.european-lisp-symposium.org/ The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 10th European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Language design and implementation - Language integration, inter-operation and deployment - Development methodologies, support and environments - Educational approaches and perspectives - Experience reports and case studies We invite submissions in the following forms: Papers: Technical papers of up to 8 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 2 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. The symposium will also provide slots for lightning talks, to be registered on-site every day. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. The conference proceedings will be published in the ACM Digital Library. Submissions should be uploaded to Easy Chair, at the following address: https://www.easychair.org/conferences/?conf=els17 Note: to help us with the review process please indicate the type of submission by entering either "paper", "demo", or "tutorial" in the Keywords field. Important dates: - 30 Jan 2017 Submission deadline - 27 Feb 2017 Notification of acceptance - 20 Mar 2017 Final papers due - 03-04 Apr 2017 Symposium Programme chair: Alberto Riva, University of Florida, USA Programme committee: Marco Antoniotti, Università Milano Bicocca, Italy Marc Battyani, FractalConcept Theo D'Hondt, Vrije Universiteit Brussel, Belgium Marc Feeley, Université de Montreal, Canada Stelian Ionescu, Google Rainer Joswig, Independent Consultant, Germany António Menezes Leitão, Technical University of Lisbon, Portugal Nick Levine, RavenPack Henry Lieberman, MIT, USA Mark Tarver, Shen Programming Group Jay McCarthy, University of Massachusetts Lowell, USA Christian Queinnec, Université Pierre et Marie Curie, France François-René Rideau, Bridgewater Associates, USA Nikodemus Siivola, ZenRobotics Ltd Alessio Stalla, Università degli Studi di Genova, Italy Search Keywords: #els2017, ELS 2017, ELS '17, European Lisp Symposium 2017, European Lisp Symposium '17, 10th ELS, 10th European Lisp Symposium, European Lisp Conference 2017, European Lisp Conference '17 -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

[cmucl-imp] Snapshot 2016-12
by Raymond Toy 03 Dec '16

03 Dec '16

Snapshot 2016-12 has been tagged and binaries will be uploaded soon. See https://gitlab.common-lisp.net/cmucl/cmucl/wikis/Home#snapshot-2016-12 for the latest news. In particular * Ticket #36 fixed: encode-universal-time signals error * Ticket #26 fixed: The cmucl that never sleeps -- Ray

1 0

[cmucl-imp] 10th European Lisp Symposium, April 3-4 2017, Brussels, Belgium
by Didier Verna 07 Nov '16

07 Nov '16

ELS'17 - 10th European Lisp Symposium VUB - Vrije Universiteit Brussel Belgium April 3-4, 2017 In co-location with <Programming> 2017 http://www.european-lisp-symposium.org/ The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 10th European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Language design and implementation - Language integration, inter-operation and deployment - Development methodologies, support and environments - Educational approaches and perspectives - Experience reports and case studies We invite submissions in the following forms: Papers: Technical papers of up to 8 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 2 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. The symposium will also provide slots for lightning talks, to be registered on-site every day. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. The conference proceedings will be published in the ACM Digital Library. Important dates: - 30 Jan 2017 Submission deadline - 27 Feb 2017 Notification of acceptance - 20 Mar 2017 Final papers due - 03-04 Apr 2017 Symposium Programme chair: Alberto Riva, University of Florida, USA Programme committee: tba Search Keywords: #els2017, ELS 2017, ELS '17, European Lisp Symposium 2017, European Lisp Symposium '17, 10th ELS, 10th European Lisp Symposium, European Lisp Conference 2017, European Lisp Conference '17 -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

[cmucl-imp] CMUCL 21b
by Raymond Toy 09 Oct '16

09 Oct '16

It's October and CMUCL 21b has been release. Binaries will be uploaded shortly. For what's changed, see the full 21b release notes: https://gitlab.common-lisp.net/cmucl/cmucl/wikis/Release21b -- Ray

1 0

[cmucl-imp] Snapshot 2016-09
by Raymond Toy 05 Sep '16

05 Sep '16

Just in time for Labor day, we have the 2016-09 snapshot. See https://gitlab.common-lisp.net/cmucl/cmucl/wikis/Home#snapshot-2016-09 for the latest news. In particular * Issue #25 fixed: Issue with ext:run-program and string streams * Issue #27 fixed: Regression: ASDF test failures * Issue #28 fixed: Recursive function definition during cross-compile Binaries will be uploaded soon. -- Ray

1 0

Re: [cmucl-imp] Debian bug 821150: problems with the PCL license [resend]
by Raymond Toy 26 Aug '16

26 Aug '16

On Thu, Aug 25, 2016 at 4:33 AM, Peter Van Eynde <pvaneynd(a)debian.org> wrote: > > What I want to add is: > Add this where? > > > Copyright of PCL: > > > > ;;; ************************************************************ > ************* > > ;;; Copyright (c) 1985, 1986, 1987, 1988, 1989, 1990 Xerox Corporation. > > ;;; All rights reserved. > > ;;; > > ;;; Use and copying of this software and preparation of derivative works > > ;;; based upon this software are permitted. Any distribution of this > > ;;; software or derivative works must comply with all applicable United > > ;;; States export control laws. > > ;;; > > ;;; This software is made available AS IS, and Xerox Corporation makes no > > ;;; warranty about the software, its performance or its conformity to any > > ;;; specification. > > ;;; > > ;;; Any person obtaining a copy of this software is requested to send > their > > ;;; name and post office or electronic mail address to: > > ;;; CommonLoops Coordinator > > ;;; Xerox PARC > > ;;; 3333 Coyote Hill Rd. > > ;;; Palo Alto, CA 94304 > > ;;; (or send Arpanet mail to CommonLoops-Coordinator.pa(a)Xerox.arpa) > > ;;; > > ;;; Suggestions, comments and requests for improvements are also welcome. > > ;;; ************************************************************ > ************* > > > > This last part is considered a request, not an obligation by the > > community. The email address is no longer in operation and as far > > as we know nobody at Xerox is working on PCL anymore. > > > > You can ignore this request. > > Would it make sense to create a newer version then 21a? > I don't quite understand this question either. But FWIW, I'm looking to do 21b in a month or two. -- Ray

2 2

[cmucl-imp] Debian bug 821150: problems with the PCL license [resend]
by Peter Van Eynde 26 Aug '16

26 Aug '16

Hello team, I fear that someone noticed a problem with the license of the PCL files in cmucl. The license reads (for example from https://gitlab.common-lisp.net/cmucl/cmucl/blob/master/src/pcl/boot.lisp) > ;;; ************************************************************************* > ;;; Copyright (c) 1985, 1986, 1987, 1988, 1989, 1990 Xerox Corporation. > ;;; All rights reserved. > ;;; > ;;; Use and copying of this software and preparation of derivative works > ;;; based upon this software are permitted. Any distribution of this > ;;; software or derivative works must comply with all applicable United > ;;; States export control laws. > ;;; > ;;; This software is made available AS IS, and Xerox Corporation makes no > ;;; warranty about the software, its performance or its conformity to any > ;;; specification. > ;;; * ;;; Any person obtaining a copy of this software is requested to send their * ;;; name and post office or electronic mail address to: * ;;; CommonLoops Coordinator * ;;; Xerox PARC * ;;; 3333 Coyote Hill Rd. * ;;; Palo Alto, CA 94304 * ;;; (or send Arpanet mail to CommonLoops-Coordinator.pa(a)Xerox.arpa) * ;;; * ;;; Suggestions, comments and requests for improvements are also welcome. > ;;; ************************************************************************* the problem is the part marked by *, this is a requirement not compatible with the DFSG. In addition the email and I guess address is dead. I've noticed that sbcl never had this clause, and I assume that we can remove it without someone complaining? Best regards, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|

5 10