?? backend-parms.lisp
字號:
;;;; that part of the parms.lisp file from original CMU CL which is defined in;;;; terms of the BACKEND structure;;;;;;;; FIXME: When we break up the BACKEND structure, this might be mergeable;;;; back into the parms.lisp file.;;;; This software is part of the SBCL system. See the README file for;;;; more information.;;;;;;;; This software is derived from the CMU CL system, which was;;;; written at Carnegie Mellon University and released into the;;;; public domain. The software is in the public domain and is;;;; provided with absolutely no warranty. See the COPYING and CREDITS;;;; files for more information.(in-package "SB!VM");;;; compiler constants(def!constant +backend-fasl-file-implementation+ :x86)(setf *backend-register-save-penalty* 3)(setf *backend-byte-order* :little-endian);;; KLUDGE: It would seem natural to set this by asking our C runtime;;; code for it, but mostly we need it for GENESIS, which doesn't in;;; general have our C runtime code running to ask, so instead we set;;; it by hand. -- WHN 2001-04-15;;;;;; Actually any information that we can retrieve C-side would be;;; useless in SBCL, since it's possible for otherwise binary;;; compatible systems to return different values for getpagesize().;;; -- JES, 2007-01-06(eval-when (:compile-toplevel :load-toplevel :execute) (setf *backend-page-bytes* 4096));;; comment from CMU CL:;;;;;; in case we ever wanted to do this for Windows NT..;;;;;; Windows NT uses a memory system granularity of 64K, which means;;; everything that gets mapped must be a multiple of that. The real;;; page size is 512, but that doesn't do us a whole lot of good.;;; Effectively, the page size is 64K.;;;;;; would be: (setf *backend-page-bytes* 65536);;; The size in bytes of the GENCGC pages. Should be a multiple of the;;; architecture code size.(def!constant gencgc-page-bytes *backend-page-bytes*)
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -