Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
cmucl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Carl Shapiro
cmucl
Commits
c941e174
Commit
c941e174
authored
17 years ago
by
rtoy
Browse files
Options
Downloads
Patches
Plain Diff
Change fasl file version to #x19e. Use boot-19e.lisp to make this
change. No cross-compile needed.
parent
c6a064a8
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
bootfiles/19d/boot-19e.lisp
+63
-0
63 additions, 0 deletions
bootfiles/19d/boot-19e.lisp
compiler/byte-comp.lisp
+2
-2
2 additions, 2 deletions
compiler/byte-comp.lisp
with
65 additions
and
2 deletions
bootfiles/19d/boot-19e.lisp
0 → 100644
+
63
−
0
View file @
c941e174
;;;;
;;;; Boot file for changing the fasl file version numbers to 19e.
;;;;
(
in-package
:c
)
(
setf
lisp::*enable-package-locked-errors*
nil
)
;;;
;;; Note that BYTE-FASL-FILE-VERSION is a constant.
;;;
;;; (Be sure to change BYTE-FASL-FILE-VERSION in
;;; compiler/byte-comp.lisp to the correct value too!)
;;;
(
setf
(
symbol-value
'byte-fasl-file-version
)
#x19e
)
(
setf
(
backend-fasl-file-version
*target-backend*
)
#x19e
)
;;;
;;; Don't check fasl versions in the compiling Lisp because we'll
;;; load files compiled with the new version numbers.
;;;
(
setq
lisp::*skip-fasl-file-version-check*
t
)
;;;
;;; This is here because BYTE-FASL-FILE-VERSION is constant-folded in
;;; OPEN-FASL-FILE. To make the new version number take effect, we
;;; have to redefine the function.
;;;
(
defun
open-fasl-file
(
name
where
&optional
byte-p
)
(
declare
(
type
pathname
name
))
(
let*
((
stream
(
open
name
:direction
:output
:if-exists
:new-version
:element-type
'
(
unsigned-byte
8
)))
(
res
(
make-fasl-file
:stream
stream
)))
(
multiple-value-bind
(
version
f-vers
f-imp
)
(
if
byte-p
(
values
"Byte code"
byte-fasl-file-version
(
backend-byte-fasl-file-implementation
*backend*
))
(
values
(
backend-version
*backend*
)
(
backend-fasl-file-version
*backend*
)
(
backend-fasl-file-implementation
*backend*
)))
(
format
stream
"FASL FILE output from ~A.~@
Compiled ~A on ~A~@
Compiler ~A, Lisp ~A~@
Targeted for ~A, FASL version ~X~%"
where
(
ext:format-universal-time
nil
(
get-universal-time
))
(
machine-instance
)
compiler-version
(
lisp-implementation-version
)
version
f-vers
)
;;
;; Terminate header.
(
dump-byte
255
res
)
;;
;; Specify code format.
(
dump-fop
'lisp::fop-long-code-format
res
)
(
dump-byte
f-imp
res
)
(
dump-unsigned-32
f-vers
res
))
res
))
This diff is collapsed.
Click to expand it.
compiler/byte-comp.lisp
+
2
−
2
View file @
c941e174
...
...
@@ -5,7 +5,7 @@
;;; Carnegie Mellon University, and has been placed in the public domain.
;;;
(
ext:file-comment
"$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/compiler/byte-comp.lisp,v 1.4
5
200
6/11/13 15:3
6:2
9
rtoy Exp $"
)
"$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/compiler/byte-comp.lisp,v 1.4
6
200
8/01/30 18:1
6:2
0
rtoy Exp $"
)
;;;
;;; **********************************************************************
;;;
...
...
@@ -32,7 +32,7 @@
;;;; Fasl file format:
(
defconstant
byte-fasl-file-version
#x19
d
)
(
defconstant
byte-fasl-file-version
#x19
e
)
(
let*
((
version-string
(
format
nil
"~X"
byte-fasl-file-version
)))
(
sys:register-lisp-feature
(
intern
(
concatenate
'string
"CMU"
version-string
)
:keyword
))
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment