GitLab

at 2016-10-06T19:24:46-07:00

Initial version.

Download cmucl binaries.

Use correct syntax

Add test job

Print more info for dynamic space lossage

If we get dynamic space lossage, print out the actual address and the
expected addresses for the dynamic space so we can see what happened.
This is really useful if you change the dynamic space address but
didn't update everything correctly.

Fix #40: Move start of heap space higher

This is a workaround for issue #40.  By moving the start of the heap
to a higher address, we can still run on older systems (albeit with
reduced max heap size), and run on newer systesm where the C code is
now mapped at or overlapping the (old) heap start.  Arbitrarily choose
0x60000000 as a compromise.

This also requires moving the foreign linkage start to a different
address because the old address overlaps the new C area.

Ideally, we could fix this if we could map the heap wherever the OS
wants to put it, but we're not there yet.

Use boot-2017-04.lisp to bootstrap this change from the 2017-04
snapshot.

Add handler-bind to auto restart

Changing defconstant's signal an error.  Add a handler-bind to restart
and continue with the changed values.

Rename to boot-2017-04-1.lisp

Merge branch 'rtoy-fix-40-map-heap-higher' into 'master'

Fix #40: Move start of heap space higher

Closes #40

See merge request !21
Fix compiler warning about else

Add braces around the else clause that's indented as if it were part
of the else clause.  Inspection of the algorithm indicates that this
is probably the intended code and in this case doesn't change what
gets executed because the following statements would have been anyway.

Also verified a few random values that `(asin x)` and `(asin (float x
1w0))` produce the same values.  Only need to test 2^-27 <= x < 0.5.

Merge branch 'master' into rtoy-gitlab-ci

Use wget instead of curl

Install wget

Install bzip2 so we can untar the cmucl tarballs

More setup for building cmucl

 - untar the snapshot into the snapshot directory
 - git clone the cmucl repo

Use the correct paths when untarring.

Need to install git.

While we're at it install make, gcc, and gcc 32-bit.

Build cmucl and run tests

Update snapshot to 2017-04 snapshot too.

Oops. Use correct tarball names

Add some debugging stuff.

 - Print out the SHELL
 - Set prompt to include PWD
 - Where is `time` and why can't the shell find it?

More debugging to see what we have

Don't need to do a git clone; install /usr/bin/time too.

The runner already has the git repo checked out at $PWD, so we're
ready to go.

Try to install time so build.sh will run.

Use correct path to the snapshot build

Need to install bc

Needed to update lisp/version.

Add pipeline status to readme
Merge branch 'master' into rtoy-gitlab-ci

Use correct pipeline marker for gitlab-ci branch
More testing of CI

 - Don't need to install git anymore
 - exit early from build script to see if that makes the test fail.

Remove debugging stuff and early exit

 - Early exit (with non-zero exit code) does cause the pipeline to
   fail, as expected.

Install git (again)

While not strictly necessary, make-dist.sh uses git to determine a
default lisp-implmenetation-version.  We could just use -V to do that,
but I think it's best to have git so that the pipeline looks as much
like normal development as possible.

Make test fail to see how pipeline works.

Revert change.

The failed test causes the pipeline to fail, as expected.

Merge branch 'rtoy-gitlab-ci' into 'master'

Enable gitlab continuous  integration

See merge request !22
Point pipeline status to the master branch.

Was pointing to the rtoy-gitlab-ci branch, but we want this to be the
status of the master branch.

Fix #41: Report proper process status

The main problem is that we weren't calling wait3 with WCONTINUED so
that we would be signaled when the process continues.  And we also
need to check that result of wait call was WCONTINUED>

Replace the wait3 routine with a C routine (prog_status) so we don't
have to deal with the OS-specific flags.  This function basically
returns what the lisp function wait3 did.

Use this function in GET-PROCESSES-STATUS-CHANGES.

 - runprog.c:
   - Add prog_status
 - run-program.lisp:
   - Use prog_status instead of wait3
 - issues.lisp:
   - Add basic test

Fix up minor issues in implementation

 - process-alive-p should return T for continued processes
 - Simplify prog-status slightly by making the status code array start
   :signaled instead of nil.
 - Update prog_status with enum to specify the codes to make it
   clearer what they mean and to make it clearer that it matches the
   expectations in prog-status.

Merge branch 'rtoy-fix-issue-41' into 'master'

Fix #41: Report proper process status

Closes #41

See merge request !23
Clean up prog_status

 - If `waidpid` returns 0 or -1, we should return.
 - Make the fprintf message a bit clearer on what's happening when we
   have some kind of status that we didn't handle.

Remove wait3 stuff

`wait3` is removed along with alien routine and the constants.

Fix #44: Add docstrings for process accessors

Adds docstrings for the exported process accessors:
`process-pid`, `process-exit-code`, `process-core-dumped`,
`process-pty`, `process-input`, `process-output`, `process-error`,
`process-status-hook`, `process-plist`.

Merge branch 'rtoy-fix-44-add-docstrings-process' into 'master'

Fix #44: Add docstrings for process accessors

Closes #44

See merge request !24
Regenerate do to new docstrings

Update from logs

Fix #45: Handle relative paths in `run-program`

This is basically the solution proposed by Elias Pipping with a few
minor tweaks.

    - In `run-program`, don't merge `program` with the "path:"
      search-list.  `spawn` will handle this.
    - In `spawn`, if the first call to execve fails, instead of trying
      "/bin/sh", use "/usr/bin/env" which will use the user's PATH if
      necessary to find the program.

Add test for issue #45

Add the tests given in issue #45.

Ignore test directory needed for issue.45 test

Regenerated

Merge branch 'rtoy-fix-45-run-program-paths' into 'master'

Fix #45 :Handle relative paths in `run-program`

Closes #45

See merge request cmucl/cmucl!25
Update to ASDF version 3.3.0

Regenerate piglatin translations

[ci skip]

Note that the included asdf version is 3.3.0

[ci skip]

Rename stdin/stdout/stderr to proc_*

Because we include stdio.h now, Solaris defines stdin, stdout, and
stderr in a way that they can't be used to name the args to the spawn
function.  Hence rename these args.

Move defsystem for pcl-tests to its own file.

The upgrade to ASDF 3.3.0 broke the pcl-tests; this version doesn't
like having the defsystem in the same file.  Thus, move the defsystem
to its own file and load it up in pcl.lisp (via require).

Update paths for snapshot-2017-10

Download the 2017-10 binaries and update build.sh options to build
with this snapshot.

Release 21c

Use `-B boot-21c` to bootstrap the release from 21b to 21c.

- 21b/boot-21c.lisp:
 - Add boot-21c.lisp to update the version number
- compiler/byte-comp.lisp
 - Update the actual version number

Add -B flag to bootstrap the release number change

Remove WIP.

Add release-21d.md release notes.

Rename release-21c.txt to .md.

Add some additional markup.

* Strike out the closed tickets
* Color (maybe?) the WIP in red.

More markup.

More markdown changes

Merge branch 'rtoy-convert-release-notes-to-md' into 'master'

Convert release-21c.txt to md file

See merge request cmucl/cmucl!26
Merge branch 'master' into 21c-branch

Remove WIP and fix typo.

Fix up markdown markup

Merge branch '21c-branch' into 'master'

21c branch

See merge request cmucl/cmucl!27
Download the 21c release for CI

Set tag for linux

These commands currently only work on linux.  Set a tag to see if this
works to enable the linux runner.

Fix syntax errors.

Validated via ci lint.

Set up stages

Let's see how that goes.

Put everything in one job with a linux tag.

Add osx support.

OSX: Download binaries and build.

Run tests on osx for real

Merge branch 'master' into rtoy-rework-ci

# Conflicts:
#	.gitlab-ci.yml

Merge branch 'rtoy-rework-ci' into 'master'

Update CI to support linux and osx runners

See merge request cmucl/cmucl!28
Increase buffer size to prevent writing past the end

The char buffer size is potentially too small and it's possible to
write past the end of the buffer with a large integer.

Fixes a compiler warning.

Fix indentation to make scoping clearer.

Compiler warns that indentation makes the scope of the for loop
unclear.  Indent the code to make it clear.

Update to asdf 3.3.1

Add asdf 3.3.1 docs

[skip-ci]

Update release notes

Initial support for xoroshiro128+ RNG

Not yet integrated but the basic vop and other methods do work and
produce the same output as the reference C code (not included).

Initial implementation of xoroshiro rng

Not yet tested or integrated.

Random cleanups and updates

Make some things work on x86:
* Can create a random state and initialize it to the desired state
* xoroshiro-chunk produces the correct values for the first few calls

Compile and load xoroshiro rng

Make xoroshiro rng available in the core.  Basic things work on x86
but not yet integrated in anyway.

Simplify state

Don't need an array for the cached value; (unsigned-byte 32) is a
specialized structure slot, so no consing.

Some random cleanups and comments.

Add tests for xoroshiro generator

Test portable version of xoroshiro-next

Put back the original version, optimized for x86.

Define xoroshiro-next before xoroshiro-chunk.

Fix typos add jump function

* Fix typos in names so we can call the functions.
* Add jump function to allow generating new distinct sequences.
* Add simple function to print the state using integers instead of
  doubles. (Untested.)

Add custom xoro-random-state printer

Custom printer to print the state as array of integers instead of
doubles.  Makes it easier to see and match what the C code does.

Print and set state as 64-bit integers

The xoroshiro128+ algorithm is defined using uint64_t types, but we
hack it to store the state as double-float's.  This is a bit
confusing, so add a printer to print the state as an array of two
uint64_t's.

Adjust init-xoro-state to allow initializing the state using an array
of 2 64-bit ints.

Add cross-compile scripts for building xoroshiro128+.

Set version 21c now.

Bootstrap files are from 21c directory instead of 21b.

Update xoroshiro methods to standard names

Make random-mt19937 function only when :random-mt19937 is set

Disable some deftransforms for now

Add rand-xoroshiro to the build files

Compile/load rand-xoroshiro if :random-xoroshiro is a feature.

Update CI to do the required cross-compile

Update tests to match xoroshiro implementation.

Conditionalize on random-xoroshiro.

These tests test the actual implementation details of the
xoroshiro128+ generator, so conditionalize it for this generator.

Add cross script for sparc

This changes the RNG to xoroshiro128+ for sparc.

Add comment

Add documentation and inline xoroshiro-gen

Not sure about inlining that; it makes random-chunk bigger and all
callers of random-chunk bigger too.

Nice speed win, however.  A test of generating 50000000 single-float
values shows xoroshiro128+ takes 0.58 sec vs 0.98 using MT19937 on my
machine.

Remove old stuff; conditionalize on :random-xoroshiro

Document the jump function and add test.

* rand-xoroshiro.lisp:
  * Rename xoroshiro-jump to random-state-jump
  * Add documentation/comments.
* tests/rng.lisp
  * Add tests for the RNG jump function.

Modify random-state-jump to use 32-bit ints

Break the constants in the jump function into 32-bit chunks so we
operate on 32-bit integers instead of 64-bit integers.

This is a minor optimization.

Fix compiler warning in VEC-INIT-XORO-STATE

Set default value for state in VEC-INIT-XORO-STATE.  If not given,
initialize it to the correct array.

Implement vop for xoroshiro-next

Not yet working.  Cross-compile works and generates appropriate code,
but can't rebuild lisp using the cross-compiled lisp.

Remove extra trailing unmatched parenthesis

Fix logic mistakes in sparc xoroshiro impl

Also compute the array offsets just once so we're consistent between
loading and storing.

Export random-state-jump

Use the xoroshiro vop on sparc

The vop greatly speeds up the generator on sparc.  The time to
generate 10,000,000 single-floats (on a 1 GHz Ultrasparc 3i) is:

mt19937:   1.32 sec
xoroshiro: 1.03 sec

So xoroshiro is 22% faster than mt19937.

Print random state in hex

Add comment for %random-double-float to use xoroshiro-gen directly
instead of random-chunk twice.  A minor micro optimization.

Add comments.

Regenerated from sources

Fix typo in reader conditional.

Don't use the portable xoroshiro-gen on x86 and sparc!

Update release notes

Merge branch 'rtoy-xoro-default' into 'master'

Change random number generator from MT19937 to xoroshiro128+

Closes #48

See merge request cmucl/cmucl!29
RANDOM should do the same as the deftransform would do.

Make RANDOM compute the value the same way as the deftransform would
do when the arg is a 32-bit integer.

The deftransform is still currently disabled for random-xoroshiro,
though.

Merge branch 'master' into sparc64-dev

Raymond Toy pushed to branch sparc64-dev at cmucl / cmucl

Commits:

30 changed files:

The diff was not included because it is too large.