Accepted gcl 2.6.1-19 (i386 source all)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 30 Dec 2003 16:26:45 +0000
Source: gcl
Binary: gcl-doc gcl
Architecture: source i386 all
Version: 2.6.1-19
Distribution: unstable
Urgency: low
Maintainer: Camm Maguire <camm@enhanced.com>
Changed-By: Camm Maguire <camm@enhanced.com>
Description:
gcl - GNU Common Lisp compiler
gcl-doc - Documentation for GNU Common Lisp
Closes: 221774
Changes:
gcl (2.6.1-19) unstable; urgency=low
.
* Fix bug in compiler::c2labels in which *ccb-vs* was missing a ocal
rebind
* Remove duplicate tags from compiled C switch statements
* Minor merges for DARWIN support
* Path to configure to make --enable-emacsdir work
* Check for readline/readline.h header before configuring for readline
* Improve system bfd library location detection
* Make sure external gmp lib is compatible via __GNU_MP_VERSION, else
backoff to local gmp build; prepend externally defined CFLAGS into
output CFLAGS, FINAL_CFLAGS, and NIFLAGS
* Remove --enable-gmp configure option; gmp is required for GCL
* Use --enable-emacsdir in debian/rules, make sure --enable-emacsdir
and --enable-infodir work when arg contains ${prefix}
* Fix typo in chap-6.texi
* Make sure to export SGC define from config.h to cmpinclude.h -- Now
that we used optimized structures in the compiler, we need at least
the definition of SGC_TOUCH there to prevent GBC errors. FIXME --
handle header dependencies more robustly. Thanks to Robert Boyer
for the report
* Improve SGC define extraction for cmpinclude.h
* Fix variable reference errors which were occurring for compiled
local functions defined within closure-generating or other
environment stack pushing functions when safety is set to 3 (thanks
Paul Dietz for the report.). When constructing local functions and
closures within a 'mother' function, *ccb-vs* will hold the number
of closure environments stacked at the point of each closure
creation or call to a local function. This value is stored as the
cadr of a list pushed onto *local-funs*, and is read when writing
out the C code for the local function or closure, where it is used
to initialize *ccb-vs* and *initial-ccb-vs* for subsequent
processing. The latter is used as the reference point when
addressing variables in wt-ccb-vs, as the former could be still
further incremented within the closure or local function itself.
Local functions as opposed to closures do not increment *ccb-vs* and
do not push the environment. When a local function is defined
within a closure-generating flet/labels, or a tagbody or block which
pushes the environment, the value of *ccb-vs* written to the list
corresponding to the local function can be erroneously incremented
beyond the *initial-ccb-vs* value established before any environment
pushing operations were processed. It is this latter value which is
appropriate for use in wt-ccb-vs, as the local functions, unlike the
closures, receive an environment level with the mother generating
function. We therefore push *initial-ccb-vs* onto the end the list
pushed onto *local-funs* only when defining a local function, and use
it to initialize an added optional variable initialize-ccb-vs in
t3local-fun and t3local-dcfun, which default to the original ccb-vs.
We then bind *initial-ccb-vs* to this new optional parameter instead
of the former *ccb-vs, which was only appropriate for closures.
* Put in rudimentary logic for the selection of stack vs. heap storage
for bignums depending on the frame context. FIXME, this logic is
too conservative at present. SETQ_II and SETQ_IO take an additional
parameter which is malloc when *unwind-exit* is bound and contains
'frame and alloca otherwise. New macro bignum-expansion-storage.
FIXME, ensure that IDECL does not need similar modification.
* Cleanup a few compiler warnings in the compiler
* Cleanup compiler warning in alloc.c
* Eliminate unneeded transformatio of contniguous pages to other pages
on save-system.
* malloc -> gcl_gmp_alloc in recent setjmp frame protected bignum
allocation
* Add -Wa,--execstack if on an exec-shield enabled system, can be
explicitly added otherwise by setting the CFLAGS variable before the
configure step
* Better execstack flag handling in configure
* Allow for commas in CFLAGS in sed command writing *cc*
* Preliminary gprof profiling support
* Rework html documentation generation and installation, Closes:
#221774
* Remove parentheses from setf class-name info node in chap-7.texi
Files:
d95b02323eb3d75214bbe054daaf6210 600 interpreters optional gcl_2.6.1-19.dsc
d6050e46ab89eb40df2a0e076f7181bc 9395797 interpreters optional gcl_2.6.1-19.tar.gz
258fd1cdfbb488226fa5f9c8f599cfdb 3212134 doc optional gcl-doc_2.6.1-19_all.deb
6fbdea28ff2e094ab89d3abb889228f9 16206964 interpreters optional gcl_2.6.1-19_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/8d9wczG1wFfwRdwRAoW3AJ9s8XT09pxvzyiscQ3fLzZcoSNVjQCgijNH
529fdlZ88JcAYBsUyFdTbps=
=nzCh
-----END PGP SIGNATURE-----
Accepted:
gcl-doc_2.6.1-19_all.deb
to pool/main/g/gcl/gcl-doc_2.6.1-19_all.deb
gcl_2.6.1-19.dsc
to pool/main/g/gcl/gcl_2.6.1-19.dsc
gcl_2.6.1-19.tar.gz
to pool/main/g/gcl/gcl_2.6.1-19.tar.gz
gcl_2.6.1-19_i386.deb
to pool/main/g/gcl/gcl_2.6.1-19_i386.deb
Reply to: