Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.


sbcl Log

Commit Date  
[25c176] (3.7 kB) by Francois-Rene Rideau Francois-Rene Rideau , pushed by Juho Snellman Juho Snellman

Deliver each contrib as a single FASL. Don't implicitly require ASDF or source code at runtime.

Also, move contrib output to obj/sbcl-home/, asdf cache to obj/asdf-cache/
Update sb-grovel and other contribs and their tests for asdf3.

Fixes lp#1132254.

2013-10-17 01:10:58 View
[2b0305] (3.8 kB) by Nikodemus Siivola Nikodemus Siivola SB-COVER:REPORT signals an error for non-directory pathnames

* Based on patch by Pierre Mai.

2008-07-31 06:50:54 View
[b210be] (3.5 kB) by Juho Snellman Juho Snellman Clean up after sb-cover tests

* No point in having the install scripts install the html files
produced while running tests. This was causing problems for
some Linux distributions that require all installed files to have
completely predictable names, whereas the test output files
would have names that depended on the exact build directory name.

2008-06-02 02:03:59 View
[77a7ce] (3.4 kB) by Juho Snellman Juho Snellman ensure that sb-cover records don't clash with constants in user code

* If a code coverage instrumentation record is coalesced with another
constant in the same file, the "we know what we're doing" comment
in INSTRUMENT-COVERAGE about modifying constants no longer applies.
Changes to the record will be reflected in the other constant too,
which is probably not what the user expected.
* Ensure that coalescing cannot happen by using a symbol internal to
SB-C as the CDR of the record (instead of NIL).
* Reported separately by Christophe Rhodes and Rahul Jain.

2008-01-02 23:07:15 View
[49e92e] (3.3 kB) by Juho Snellman Juho Snellman new contrib: sb-cover, a code coverage tool

Still somewhat experimental, so it might be changed incompatibly once
people start actually using it. Or maybe even removed, if it's not
found to be useful in practice. More documentation on interpreting
the output and on the limitations of the coverage tool will be
committed later.

* Compiler
* Instrument all forms found in the original source code
when the store-coverage-data optimization quality is larger
than 1.
* The instrumentation is fairly lightweight; just literal conses that
are modified when the form is executed.
* This requires hacking the compiler to allow modifying literals
when we know what we're doing.
* Add some extra source location tracking capabilities to handle
non-cons source forms better (though still not perfectly).
* Contrib
* Get the instrumentation data from the compiler, and create
a aggregate report + pretty annotate source code reports
(as html) from it.
* The latter uses a modified version of the source code tracking
read-table from Swank, written by Helmut Eller.

2007-05-03 03:27:55 View