- Dec 04, 2016
-
-
Raymond Toy authored
:sparc64 sources are in sparcv9. (Should we rename the directory?)
-
Raymond Toy authored
Use this with the -B option of cross-build-world.sh when cross-compiling from x86 to sparc.
-
- Dec 03, 2016
-
-
Raymond Toy authored
Copy Config.sparc_sunc to Config.sparcv9_sunc, removing the -m32 option and updating ASSEM_SRC to sparcv9-assem.S. Remove that from Config.sparc_common and put it in Config.sparc_sunc.
-
Raymond Toy authored
-
Raymond Toy authored
Pure copy of sparc files to sparcv9 directory and copy sparc-assem.S to sparcv9-assem.S No other changes made.
-
Raymond Toy authored
-
- Dec 02, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
Don't use cl:assert for the lisp-unit test; it should use lisp-unit assertions.
-
Raymond Toy authored
ieee754_rem_pio2 was not formatted according to cmucl style. Just re-indent. No other changes.
-
Raymond Toy authored
Fix #26: Use nanosleep to sleep without being interrupted First, use nanosleep to sleep instead of using select. Then handle the case of nanosleep being interrupted wherein we keep calling nanosleep with the remaining time until the desired time has elapsed. See merge request !17
-
- Dec 01, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Nov 30, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Nov 29, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
Basically used the repro case from the issue.
-
Raymond Toy authored
o Include math.h before netdb.h (from Carl) o Use ceil instead of trunc and add comment on why. o Conform to cmucl style.
-
Raymond Toy authored
lisp/os-common.c: o Implement os_sleep(double) to sleep for the given number of seconds. Uses nanosleep on all platforms to sleep, taking care to sleep more if nanosleep was interrupted. code/lispinit.lisp: code/multi-proc.lisp: o Use the new os_sleep function to sleep for the requested amount of time.
-
- Nov 11, 2016
-
-
Raymond Toy authored
Allow 1899 as a year, but also add a check that the resulting time is a non-negative integer. Add a test for this too in issues.lisp.
-
- Oct 09, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
* Update links to point to the gitlab cmucl wiki * Rephrase a bit differently since things have changed.
-
Raymond Toy authored
* Indent neatly * Run spell-checker
-
- Oct 08, 2016
-
-
Raymond Toy authored
* Update byte-fasl-file-version to #x21b * Add boot-21b.lisp bootstrap file to bootstrap the changes. With this, we're now at 21b.
-
Robert Swindells authored
-
- Oct 05, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
-
Raymond Toy authored
-
- Oct 04, 2016
-
-
Raymond Toy authored
Forgot to check this in with the fix for issue #24.
-
- Oct 03, 2016
-
-
Raymond Toy authored
Add a test for MR !15 See merge request !16
-
Elias Pipping authored
-
- Oct 02, 2016
-
-
Raymond Toy authored
Fix: directory followed symlinks with :follow-links nil I'm on Linux. I'm looking at a directory that contains both physical directories and symbolic links to directories. ### What I would expect: ```common-lisp (directory "/path/to/dir/*.*" :check-for-subdirs t :follow-links t :truenamep nil) ``` will show both (because it will show everything in that directory) and mark both types as directories with trailing slashes. ```common-lisp (directory "/path/to/dir/*.*" :check-for-subdirs t :follow-links nil :truenamep nil) ``` will again show all files but only add trailing slashes to the physical subdirectories. ### What actually happens Both commands give me the same output. That is because `directory` calls `unix:unix-file-kind` to categorise files into directory/link/etc., which internally calls `stat`. It will only use `lstat` if the second, optional argument is passed as **t**. In default mode (the way it currently is) symlinks to directories will be assigned the type :directory regardless of the flags passed to `directory`. I believe the change contained in this merge request is thus the correct fix. See merge request !15
-
- Oct 01, 2016
-
-
Robert Swindells authored
-
Robert Swindells authored
-
Robert Swindells authored
-
Raymond Toy authored
Fix #29: Update processing of command line Several related changes here. - If `:process-command-line` is NIL, `*command-line-strings*` and `*command-line-application-arguments*` weren't getting updated. They should get updated so that the resulting core can get updated command line options instead of using the values dumped with the core. The command line switch demons are still not run, as before. - Add a `:quiet` option as if `-quiet` were given. See merge request !13
-
- Sep 28, 2016
-
-
Elias Pipping authored
-
- Sep 27, 2016
-
-
Raymond Toy authored
Fix some typos too.
-