- Sep 08, 1997
- Sep 07, 1997
-
-
dtc authored
start of the body to support their checking within the body, and restore these exceptions on exit to allow nesting.
-
dtc authored
-
dtc authored
registers off the stack to empty it rather than re-initialising the whole NPX state. This has the advantage that the flagged exceptions are preserved (they were just being flushed), and it also a little quicker.
-
- Sep 05, 1997
-
-
dtc authored
-
dtc authored
-
dtc authored
optimisation opportunity; revert to the original version for the integer case.
-
dtc authored
-
dtc authored
o Optimizer for + recognizes the case of (+ x x). The old behavior produced a result that was wider than necessary. o Optimizer for - recognizes (- x x) is always 0. o Optimizer for / recognizes (/ x x) is 1, usually. However, if x can contain 0, we don't return 1 as the result because 0 / 0 is not 1. (Perhaps if safety = 0, we could ignore this possibility, and just say the result is always 1?) o Optimizer for abs understands union types. This also corrects the bug that abs of a union type returned NUMBER instead of (REAL 0), as it should have.
-
dtc authored
o Added optimizers for ftruncate, ffloor, and fceiling. o Most elementary functions can now handle union types and appropriate bounds are returned. This includes truncate, floor, ceiling, and float. o Some bugs in the optimizers were also fixed because union types are handled now. In particular most functions returned (FLOAT) (or subtype thereof) when in fact the answer should have been (OR FLOAT (COMPLEX FLOAT)). o The optimizer for log now handles the case of (log x y) and returns appropriate bounds for it. (It used to give up in this case.) o The optimizer for atan and phase works better and handles more cases.
-
- Sep 04, 1997
- Sep 03, 1997
-
-
dtc authored
loaded.
-
dtc authored
with PCL loaded.
-
dtc authored
pcl version can simply replace the lisp version now.
-
dtc authored
extension.
-
dtc authored
coerce, was being lost. Patch result-type-or-lose to use (type-specifier (specifier-type type)) to find a suitable result type return than just returning 'vector.
-
- Sep 02, 1997
-
-
dtc authored
from Raymond Toy.
-
- Sep 01, 1997
-
-
dtc authored
modified; the result type will in general be a sequence not a consed-sequence.
-
- Aug 30, 1997
-
-
dtc authored
-
dtc authored
the doc-type argument is no longer optional.
-
dtc authored
wrapped in a list, which was inconsistent with other doc. initargs to shared-initialize.
-
dtc authored
improves the handling of special case.
-
dtc authored
floating point exceptions disabled. It avoids the overhead of {set,get}-floating-point-modes, saving some consing and generally giving smaller code. Exploit this new macro where {set,get}-floating-point-modes has been used.
-
dtc authored
suspect life specs. Removed the FP exception sticky bit code, can now clear the exceptions.
-
- Aug 29, 1997
-
-
dtc authored
function; causes a loop.
-
- Aug 26, 1997
- Aug 25, 1997
-
-
pw authored
a few days ago. Somehow these bits didn't get included.
-
- Aug 24, 1997
-
-
pw authored
and account for fact that FreeBSD does not have a OCRNL termios flag which was used by Hemlock.
-
dtc authored
which the result can be determined from the argument type. This stops compiler warning messages produced by the with-array-data macro when the array is known not to be a subtype of (simple-array * (*)).
-
dtc authored
(subtypep '(alien (* t)) '(alien (* t))) which caused other failures in the type system.
-
- Aug 23, 1997
-
-
pw authored
Here's a patch to add more complete support of tty functions and parameters to the unix interface (including in particular some more tc* series functions as well as cf[gs]et[io]speed and more tty modes), as well as o_nonblock. The flags argument to unix-open is changed to be a fixnum because some hp flags in particular are larger than 16 bits. I don't have access to an alpha/osf1 machine, so I couldn't put in support for it in the tty stuff, and I only have access to the header files and source for linux and freebsd so the changes for it are untested (although I would be surprised if they broke anything for reasons other than typos). For the feature conditionals on the symbol entries in the exports list in unix.lisp, I used svr4 only for symbols which are listed in the SVID, and an explicit list of machines for other symbols. I also consolidated the termios definitions based on some standards and include file perusal, along with a little inference (see the comment). This patch itself was generated by undoing some other changes I made for the sgi dso patch I posted earlier, and so has not been tested in this form, but the changes have been tested extensively under 17f on HPUX 10.10 (an earlier form of the changes), as well as (somewhat less) under 18a on IRIX 6.2 and 6.3 (R5000 O2 and R4400 Onyx respectively) and Solaris 2.5.1 on an ultrasparc (minimally: it compiles). This patch makes all machines define unix::+NCCS+ instead of unix::+NCC+, so if you're on a machine which used to define the latter, you'd need to put (defconstant unix::+nccs+ unix::+ncc+) in your bootstrap.lisp.
-
pw authored
foreign functions taking floating-point arguments after integer arguments but before the fourth argument (more or less; mips has unusual C calling conventions), and making cmucl work on IRIX 6.2 on the Onyx (where the system page size has changed). I've included the patches below, along with some discussion of the changes and a couple of problems with cmucl's interaction with dynamic loading. Also, there's a misc change to make ioctls work (I'm not sure for what version the released code worked, but it doesn't work on anything I have). The patches do not fix the R10000; cmucl continues to not work on it (O2 and Octane). The fixes make cmucl on the sgi use shared libraries so it can use dlopen et al in load-foreign; this is based on the solaris implementation. The problem with this is that the addresses of foreign variables are included directly in the dumped lisp image (without relocation on loading), which might result in a problem if cmucl is run with newer shared libraries than those it was compiled and dumped with. As far as I can tell, for the SGI at least, this does not affect function calls because the addresses used (and included in the dumped image) are those of stub routines that jump to the actual routines, thus are located in the executable proper rather than in the shared libraries, and so shouldn't be changed by a new version of the shared library. Unfortunately, this is not the case for global variables. Fortunately, there appear to only be two foreign variables used by cmucl in any of its system code winding up in the dumped image: errno and tzname. Apparently, Solaris relocates data references in dsos to match the program, while IRIX relocates data references in the program to match the dso. Thus, on Solaris, you don't need to do anything special for cmucl to work with a newer runtime libc, but on IRIX it gets the wrong value of errno and tzname. Unfortunately, the address of errno is different between irix 6.2, 6.3, and 6.4 (all of which we have to have because SGI doesn't have a single cross-platform OS version yet), which would require a different lisp.core for each machine (you just need to run mk-lisp, not recompile) if it weren't for the hack below. But fortunately again, a lisp compiled for one version seems to be able to run on another version well enough to generate the new lisp.core (presumably the worst that would happen is that error messages could be confusing). It would be really nice to avoid this problem. Perhaps some kind of relocation table could be added to the dumped image format? I don't know enough about the system to know how possible or ridiculous that suggestion is, unfortunately. Is the Solaris behavior guaranteed to be the same in future releases? If not, or if any other platforms have the irix behavior, this might become a more general problem. In the meantime, we use a hack: we *define* errno in undefineds.c rather than just referencing it; this results in warnings from the linker, but it resolves the conflict in favor of the definition in the program, relocating libc to match, thus fixing this problem for errno. The other global variables, tzname et al, can't be fixed this way as easily because they're listed as weak symbols, essentially aliases for the real symbol, so redefining them wouldn't cause libc to reference the new version. Thus, as long as you don't use tzname, there's no problem right now (although there may be if any other library global variables are used in cmucl in the future). The definition of tzname is in a progn preceeded by a comment which says not to use it, so hopefully it's not in fact used and therefore not a problem. These patches have been tested on an R5000 O2 running irix 6.3 and a dual R4400 Onyx running irix 6.2. A previous version of these patches (for 17f) was tested on the onyx when it was running 5.3 (I think, maybe 5.2). The patches here are from the main branch of the CVS tar as of August 13. Incidentally, it was quite painful figuring out how to compile and bootstrap the current sources under the distributed irix 18a binary, even without trying :new-random or :signed-array (which I haven't tried to do yet); it might be nice to put a newer binary up...
-
- Aug 22, 1997
-
-
pw authored
Here are a bunch of fixes and enhancements to motif, including implementations of the XtIs* functions, XtNameToWidget, an xt-widget-parent that will find the parent even if it's not known to lisp (eg, was created by the motif library implicitly), a fix for get-values on big-endian machines when the resource size is less than an int, a fix to the hashtable mapping motif widget ids to lisp records of them, addition of certain resource type definitions, fixing many callbacks to prevent null-dereferencing which causes crashes on IRIX, a hack to treat the size of booleans more correctly because they aren't necessarily ints (a design problem prevents an easy, cleaner fix), and a fix to prevent motifd leaving children on HPUX.
-
- Aug 21, 1997
-
-
pw authored
-
- Aug 16, 1997
-
-
dtc authored
-