Mercurial > hg > xemacs-beta
view lisp/itimer-autosave.el @ 4921:17362f371cc2
add more byte-code assertions and better failure output
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-02-03 Ben Wing <ben@xemacs.org>
* alloc.c (Fmake_byte_code):
* bytecode.h:
* lisp.h:
* lread.c:
* lread.c (readevalloop):
* lread.c (Fread):
* lread.c (Fread_from_string):
* lread.c (read_list_conser):
* lread.c (read_list):
* lread.c (vars_of_lread):
* symbols.c:
* symbols.c (Fdefine_function):
Turn on the "compiled-function annotation hack". Implement it
properly by hooking into Fdefalias(). Note in the docstring to
`defalias' that we do this. Remove some old broken code and
change code that implemented the old kludgy way of hooking into
the Lisp reader into bracketed by `#ifdef
COMPILED_FUNCTION_ANNOTATION_HACK_OLD_WAY', which is not enabled.
Also enable byte-code metering when DEBUG_XEMACS -- this is a form
of profiling for computing histograms of which sequences of two
bytecodes are used most often.
* bytecode-ops.h:
* bytecode-ops.h (OPCODE):
New file. Extract out all the opcodes and declare them using
OPCODE(), a bit like frame slots and such. This way the file can
be included multiple times if necessary to iterate multiple times
over the byte opcodes.
* bytecode.c:
* bytecode.c (NUM_REMEMBERED_BYTE_OPS):
* bytecode.c (OPCODE):
* bytecode.c (assert_failed_with_remembered_ops):
* bytecode.c (READ_UINT_2):
* bytecode.c (READ_INT_1):
* bytecode.c (READ_INT_2):
* bytecode.c (PEEK_INT_1):
* bytecode.c (PEEK_INT_2):
* bytecode.c (JUMP_RELATIVE):
* bytecode.c (JUMP_NEXT):
* bytecode.c (PUSH):
* bytecode.c (POP_WITH_MULTIPLE_VALUES):
* bytecode.c (DISCARD):
* bytecode.c (UNUSED):
* bytecode.c (optimize_byte_code):
* bytecode.c (optimize_compiled_function):
* bytecode.c (Fbyte_code):
* bytecode.c (vars_of_bytecode):
* bytecode.c (init_opcode_table_multi_op):
* bytecode.c (reinit_vars_of_bytecode):
* emacs.c (main_1):
* eval.c (funcall_compiled_function):
* symsinit.h:
Any time we change either the instruction pointer or the stack
pointer, assert that we're going to move it to a valid location.
This should catch failures right when they occur rather than
sometime later. This requires that we pass in another couple of
parameters into some functions (only with error-checking enabled,
see below).
Also keep track, using a circular queue, of the last 100 byte
opcodes seen, and when we hit an assert failure during byte-code
execution, output the contents of the queue in a nice readable
fashion. This requires that bytecode-ops.h be included a second
time so that a table mapping opcodes to the name of their operation
can be constructed. This table is constructed in new function
reinit_vars_of_bytecode().
Everything in the last two paras happens only when
ERROR_CHECK_BYTE_CODE.
Add some longish comments describing how the arrays that hold the
stack and instructions, and the pointers used to access them, work.
* gc.c:
Import some code from my `latest-fix' workspace to mark the
staticpro's in order from lowest to highest, rather than highest to
lowest, so it's easier to debug when something goes wrong.
* lisp.h (abort_with_message): Renamed from abort_with_msg().
* symbols.c (defsymbol_massage_name_1):
* symbols.c (defsymbol_nodump):
* symbols.c (defsymbol):
* symbols.c (defkeyword):
* symeval.h (DEFVAR_SYMVAL_FWD_OBJECT):
Make the various calls to staticpro() instead call staticpro_1(),
passing in the name of the C var being staticpro'ed, so that it
shows up in staticpro_names. Otherwise staticpro_names just has
1000+ copies of the word `location'.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Wed, 03 Feb 2010 08:01:55 -0600 |
parents | 41ff10fd062f |
children | 308d34e9f07d |
line wrap: on
line source
;;; itimer-autosave.el --- Autosave functions with itimers ;; Copyright status unknown ;; Maintainer: XEmacs Development Team ;; Keywords: internal, dumped ;; This file is part of XEmacs. ;; XEmacs is free software; you can redistribute it and/or modify it ;; under the terms of the GNU General Public License as published by ;; the Free Software Foundation; either version 2, or (at your option) ;; any later version. ;; XEmacs is distributed in the hope that it will be useful, but ;; WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ;; General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with XEmacs; see the file COPYING. If not, write to the Free ;; Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA ;; 02111-1307, USA. ;;; Synched up with: Not in FSF. ;;; Commentary: ;; This file is dumped with XEmacs. ;; itimer-driven auto-saves ;;; Code: ;jwz: this is preloaded so don't ;;;###autoload (defvar auto-save-timeout 960 "*Number of seconds idle time before auto-save. Zero or nil means disable auto-saving due to idleness. The actual amount of idle time between auto-saves is logarithmically related to the size of the current buffer. This variable is the number of seconds after which an auto-save will happen when the current buffer is 50k or less; the timeout will be 2 1/4 times this in a 200k buffer, 3 3/4 times this in a 1000k buffer, and 4 1/2 times this in a 2000k buffer. See also the variable `auto-save-interval', which controls auto-saving based on the number of characters typed.") ;jwz: this is preloaded so don't ;;;###autoload (defvar auto-gc-threshold (/ gc-cons-threshold 3) "*GC when this many bytes have been consed since the last GC, and the user has been idle for `auto-save-timeout' seconds.") (defun auto-save-itimer () "For use as a itimer callback function. Auto-saves and garbage-collects based on the size of the current buffer and the value of `auto-save-timeout', `auto-gc-threshold', and the current keyboard idle-time." (if (or (null auto-save-timeout) (<= auto-save-timeout 0) (eq (minibuffer-window) (selected-window))) nil (let ((buf-size (1+ (ash (buffer-size) -8))) (delay-level 0) (now (current-time)) delay) (while (> buf-size 64) (setq delay-level (1+ delay-level) buf-size (- buf-size (ash buf-size -2)))) (if (< delay-level 4) (setq delay-level 4)) ;; delay_level is 4 for files under around 50k, 7 at 100k, 9 at 200k, ;; 11 at 300k, and 12 at 500k, 15 at 1 meg, and 17 at 2 meg. (setq delay (/ (* delay-level auto-save-timeout) 4)) (let ((idle-time (if (or (not (consp last-input-time)) (/= (car now) (car last-input-time))) (1+ delay) (- (car (cdr now)) (cdr last-input-time))))) (and (> idle-time delay) (do-auto-save)) (and (> idle-time auto-save-timeout) (> (consing-since-gc) auto-gc-threshold) (garbage-collect))))) ;; Look at the itimer that's currently running; if the user has changed ;; the value of auto-save-timeout, modify this itimer to have the correct ;; restart time. There will be some latency between when the user changes ;; this variable and when it takes effect, but it will happen eventually. (let ((self (get-itimer "auto-save"))) (or self (error "auto-save-itimer can't find itself")) (if (and auto-save-timeout (> auto-save-timeout 4)) (or (= (itimer-restart self) (/ auto-save-timeout 4)) (set-itimer-restart self (/ auto-save-timeout 4))))) nil) (defun itimer-init-auto-gc () (or noninteractive ; may be being run from after-init-hook in -batch mode. (get-itimer "auto-save") ;; the time here is just the first interval; if the user changes it ;; later, it will adjust. (let ((time (max 2 (/ (or auto-save-timeout 30) 4)))) (start-itimer "auto-save" 'auto-save-itimer time time)))) (cond (purify-flag ;; This file is being preloaded into an emacs about to be dumped. ;; So arrange for the auto-save itimer to be started once emacs ;; is launched. (add-hook 'after-init-hook 'itimer-init-auto-gc)) (t ;; Otherwise, this file is being loaded into a normal, interactive ;; emacs. Start the auto-save timer now. (itimer-init-auto-gc))) ;;; itimer-autosave.el ends here