arguments not recognized as standard options and added a description
of the same to the COMMAND-LINE OPTIONS section of the man page.
did a bit of minor cleanup elsewhere in the man page.
use.stex, scheme.1.in
original commit: a963a4dbc872be084cbe0ede3f7c361bcabedea5
bytevector-immutable-flag in computation of type-immutable-bytevector
cmacros.ss
- reallocated typed-object types, using previously unused tag #b010
for strings and giving bytevectors both #b001 and #b101 (the
latter for immutable bytevectors) so that the maximum bytevector
length on 32-bit machines is once again the most-positive fixnum.
treating bytevectors rather than strings or fxvectors (or even
vectors) special in this regard is appropriate since the maximum
number of bytes in a bytevector is maximum-length x 1 rather than
maximum-length x 4 for strings, fxvectors, and vectors on 32-bit
machines. with this change on 32-bit machines, a vector can
occupy up to 1/2 of virtual memory, strings and fxvectors 1/4,
and bytevectors 1/8.
cmacros.ss
- remade boot files
original commit: 0694b3a5223ab937379e54079bc88d57309dc51f
arguments. cp0 optimizes away a number of additional equality
operations at optimize-level 3 (including bytevector=?) when
applied to the same variable references, as it already did for
eq?, eqv?, and equal?, at all optimize levels.
cpnanopass.ss, cp0.ss, primdata.ss,
cp0.ms
- updated bullyx patches
patch*
- updated release notes and tweaked user's guide.
release-notes.stex, objects.stex
original commit: e90c39a72563eafa4fccaf1d197060bf20aa552f
to simplify ($fxu< (most-positive-fixnum) e) => (fx< e 0) so we
don't have any incentive in special casing length checks where
the maximum length happens to be (most-positive-fixnum).
5_4.ss, 5_6.ss, bytevector.ss, cmacros.ss, cp0.ss, cpnanopass.ss,
mkheader.ss, primdata.ss, prims.ss,
fasl.c, gc.c, types.h
root-experr*, patch*
original commit: 9eb63deda025fd4560b54746b21a881c01af46d6
is a fixnum and added meta-asserts to verify that it is in a couple of
others, to facilitate future changes to vector typing. vectors are
now treated essentially like fxvectors, strings, and bytevectors.
cmacros.ss, cpnanopass.ss, prims.ss, mkheader.ss,
alloc.c, gc.c, scheme.c
original commit: 564542d32bbae6b33cef808613238d5a4a2a8ee2
paired the 'partialx' down to just four test configurations, with one
interpreter run, to try to get the threaded builds into line with
travis-ci's timeout.
mats/Mf-base
original commit: 6d8c871cd60228755660395e96087878ca9d040f
added travis-ci automation script and a 'partialx' testing target to
allow us to perform more than a single run of testing without running
afoul of travis-ci's 50-minute build timeout. 'partialx' tests six
of the twelve configurations tested by 'allx'.
.travis.yml (new),
mats/Mf-base
original commit: fdc8dc40e95b0977ab7bc07636585b71e56802a3
floating-point register arguments as required for varargs functions
by the System V ABI.
x86_64.ss,
foreign.ms
remade boot files
original commit: c5b6fe968f890bbef3488d570756cbe8da211326
Check both the beginning file pointer (bfp) and end file pointer (efp)
of the source location associated with a profile counter when updating
its count.
Assuming that each expression has a unique bfp with respect to profiling
seems to give accurate execution counts for s-expression-based source
locations as in Scheme, but causes problems when targeting other kinds
of syntax. For instance, a C-style function call, referencing the called
function by name, such as "fn(arg)", can logically have profile counters
associated with 1) the function name reference ("fn") and 2) the entire
function call expression ("fn(arg)"), both of which begin at the same
source location. Only the bfp is checked when updating profile counters,
so the two source locations are conflated, and only one counter is
incremented, which gives inaccurate execution counts for both locations;
approximately twice as many for one, and zero for the other.
original commit: d364b05c3c9cd2b299fc20a6f5ec255ab7bd6718
Change the foreign procedure definitions to use the more portable int
rather than integer-32. Switch to a custom port
[make-custom-binary-input/output-port] rather than a generic port
[make-input/output-port], which resulted in deleting quite a bit of
code. Fix various compiler warnings in the C code, and along the way,
fix a signedness bug in c_write that could have resulted in not writing
the full buffer (but reporting that it did) in the case of errors from
write.
examples/csocket.c, examples/socket.ss
original commit: 9dfa900b251ba480ea13b1796a58d7398146d0b9
and release notes. updated the release notes to account for a couple
of other log entries.
release_notes.stex,
intro.stex, io.stex
original commit: 7d1bbdaaccc6640e1529fdbd8b40a8ff7012bee4
4.ms, root-experr-compile-0-f-f-f
- added print-extended-identifier parameter. when #t, symbols like
1+ and +++ print without escapes.
priminfo.ss, print.ss,
6.ms
original commit: 603019ea82afda1926462214576ef92df15e43c8
that calls the current value of base-exception-handler so the handler
can be overridden, as we do in our own make files.
cafe.ss,
7.ms
original commit: 99b763e30d22b205106ef9a84ea2e0a928fd0b30
form for later passes to choke on. also fixed cp0 to print the correct
name for cpvalid when it does this.
cpvalid.ss, cp0.ss,
misc.ms
- updated the prototype for s_ee_write_char to match the definition
expeditor.c
- updated LOG and release_notes
- rebuilt boot files due to s-directory changes
original commit: 50aa8b34774a9e65e96481ae329a3f329fad7aca
allocating the thread context fails from Sactivate_thread. before
this change, the error was raised on the main thread, which resulted
in strange behavior at best. also added who argument to
S_create_thread_object to allow it to report either Sactivate_thread
or fork-thread led to the error.
externs.h, schsig.c, scheme.c, thread.c
original commit: 89691cee27ee7d5e9bffae530b6346e96f8cc7ad
change to compile on windows. unicode is not yet supported in the windows
version of the repl.
c/expeditor.c
original commit: 4d2f900b2c43a8be384444d965177f1410c2ab82
except that combining characters are not treated correctly for
line-wrapping. this addresses github issue #32 and part of issue #81.
c/expeditor.c, s/expeditor.ss
original commit: 87d4811781d7e9183f7710aa6a809b850a38454f
because these fields can be accessed from multiple threads concurrently.
Updated $yield and $thread-check in mats/thread.ms to be more tolerant of timing variability.
original commit: 0a6a1e14e7ecb9e39fa7a10a8584ed2fec24cbf4
sizes of pathnames produced by expansion of tilde (home-directory)
prefixes by replacing S_pathname, S_pathname_impl, and S_homedir
with S_malloc_pathname, which always mallocs space for the result.
one thread-safety issue involved the use of static strings for expanded
pathnames and affected various file-system operations. the other
affected the file open routines and involved use of the incoming
pathname while deactivated. the incoming pathname is sometimes if not
always a pointer into a Scheme bytevector, which can be overwritten if a
collection occurs while the thread is deactivated. the size limitation
corresponded to the use of the static strings, which were limited to
PATH_MAX bytes. (PATH_MAX typically isn't actually the maximum path
length in contemporary operating systems.) eliminated similar issues
for wide pathnames under Windows by adding S_malloc_wide_pathname.
consumers of the old routines have been modified to use the new
routines and to free the result strings. the various file operations
now consistently treat a pathname with an unresolvable home directory
as a pathname that happens to start with a tilde. eliminated unused
foreign-symbol binding of "(cs)pathname" to S_pathname.
io.c, externs.h, new_io.c, prim5.c, scheme.c, prim.c
- various places where a call to close or gzclose was retried when
the close operation was interrupted no longer do so, since this can
cause problems when another thread has reallocated the same file
descriptor.
new_io.c
- now using vcvarsall type x86_amd64 rather than amd64 when the
former appears to supported and the latter does not, as is the
case with VS Express 2015.
c/Mf-a6nt, c/Mf-ta6nt
- commented out one of the thread mats that consistently causes
indefinite delays under Windows and OpenBSD due to starvation.
thread.ms
- increased wait time for a couple of subprocess responses
6.ms
- added call to collector to close files opened during iconv mats
specifically for when mats are run under Windows with no iconv dll.
io.ms
original commit: ad44924307c576eb2fc92e7958afe8b615a7f48b
the zlib header files, since zlib's configure script can modify the
header files. removed ZlibInclude variable, which no longer serves
a purpose.
c/Mf-*, c/Makefile.*nt
- removed unnecessary datestamp.c target
c/Mf.*nt
original commit: d081c5b19a185597443f47101caa35b8c12084c7
- added a cast to eliminate warnings in c/number.c
- fixed bug in Windows version of directory-separator-predicate in s/6.ss when path-* procedures are passed a path that is not a string.
- fixed bug in s/cp0.ss on Windows with $foreign-wchar?.
- fixed spelling of non-existent
original commit: dd1b741f7572cb0d5a6210c7c796aee7c4026040
reflect the Version 9.3.1 change from sstats structures to sstats
records, with sstats times represented as time objects and sstats
bytes and counts represented as exact integers; also updated the
sstats-difference description to reflect that it no longer coerces
negative differences to zero. added a corresponding release note.
system.stex,
release_notes.stex
original commit: cd93f130c2a911d67bc19b75da0f205d50b8f6ff
