Mercurial > hg > xemacs-beta
view lisp/loaddefs.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 | 5aa1854ad537 |
children | 308d34e9f07d |
line wrap: on
line source
;;; loaddefs.el --- define standard autoloads of other files ;; Copyright (C) 1985-7, 1992-5, 1997 Free Software Foundation, Inc. ;; Maintainer: XEmacs Development Team ;; Keywords: internal ;; 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, 59 Temple Place - Suite 330, ;; Boston, MA 02111-1307, USA. ;;; Synched up with: Not synched with FSF. ;;; Commentary: ;; The following commentary is completely out of date. I would like to ;; delete it, but it serves as a useful reminder as to how things used to ;; work. ;; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;; Special formatting conventions are used in this file! ;; a backslash-newline is used at the beginning of a documentation string ;; when that string should be stored in the file lib-src/DOCnnn, not in core. ;; Such strings read into Lisp as numbers (during the pure-loading phase). ;; But you must obey certain rules to make sure the string is understood ;; and goes into lib-src/DOCnnn properly. Otherwise, the string will not go ;; anywhere! ;; The doc string must appear in the standard place in a call to ;; defun, autoload, defvar or defconst. No Lisp macros are recognized. ;; The open-paren starting the definition must appear in column 0. ;; In defvar and defconst, there is an additional rule: ;; The double-quote that starts the string must be on the same ;; line as the defvar or defconst. ;; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;; ********************************************************************** ;; You should never need to write autoloads by hand and put them here. ;; It is no longer necessary. Instead use autoload.el to maintain them ;; for you. Just insert ";;;###autoload" before defuns or defmacros you ;; want to be autoloaded, or other forms you want copied into loaddefs.el ;; (defvars, key definitions, etc.). For example, ;; ;;;###autoload ;; (defun foobar () ....) ;; ;;;###autoload (define-key global-map "f" 'foobar) ;; ;;;###autoload ;; (defvar foobar-var nil "\ ;; This is foobar-var's doc-string.") ;; Then do M-x update-file-autoloads on the file to update loaddefs.el. ;; You can also use M-x update-directory-autoloads to update the autoloads ;; in loaddefs.el for all .el files in the lisp/ directory, or M-x ;; update-autoloads-here to update the autoloads for each file that ;; already has an autoload section in this file. ;; ********************************************************************** ;;; Code: ;; These variables are used by autoloadable packages. ;; They are defined here so that they do not get overridden ;; by the loading of those packages. ;; Names in directory that end in one of these ;; are ignored in completion, ;; making it more likely you will get a unique match. (setq completion-ignored-extensions ;; this is way way way bogus. ;; completely wtf? ;; the only things that should be here are those that are ;; (a) universally recognizable, and ;; (b) obvious backup files, or ;; (c) obvious binary files that are generated on a ;; PER-SOURCE-FILE basis, so that they will actually ;; cause annoyance. This excludes executables (.exe, .com) ;; and libraries (.a, .lib, .dll). ; '(".o" ".elc" "~" ".bin" ".lbin" ".fasl" ; ".dvi" ".toc" ;".log" ; ".aux" ".a" ".ln" ; ".lof" ".blg" ".bbl" ".glo" ".idx" ".lot" ".fmt" ; ".diff" ".oi" ".class"))) '(".o" ".obj" ".elc" "~" ".bin" ".lbin" ;; #### these are doubtful, esp. the latter. ".dvi" ;; possibly doubtful, too. ".class")) ;; This needs to be redone better. -slb ;(setq debug-ignored-errors ; '(beginning-of-line ; beginning-of-buffer ; end-of-line ; end-of-buffer ; end-of-file buffer-read-only ; "\\`Previous command was not a yank\\'" ; "\\`Minibuffer is not active for completion\\'" ; "\\`No \\(following\\|preceding\\) item in .*-history\\'" ; "\\`No recursive edit is in progress\\'" ; "\\`Changes to be undone are outside visible portion of buffer\\'" ; "\\`No further undo information\\'" ; "\\`No undo information in this buffer\\'" ; "\\`Buffer modified since last undo/redo, cannot redo" ; "\\`Save not confirmed\\'" ; "\\`Canceled\\'" ; "\\`\\(Revert\\|Steal\\|Recover-file\\) cancelled\\.\\'" ; ;; comint ; "\\`Not at command line\\'" ; "\\`Empty input ring\\'" ; "\\`No history\\'" ; "\\`Not found\\'" ;; To common? ; "\\`Current buffer has no process\\'" ; ;; dabbrev ; "\\`No \\(further \\)?dynamic expansion for .* found\\.?\\'" ; ;; Completion ; "\\`To complete, the point must be after a symbol at least [0-9]* character long\\.\\'" ; "\\`The string \".*\" is too short to be saved as a completion\\.\\'" ; ;; Compile ; "\\`No more errors\\( yet\\|\\)\\'" ; ;; Gnus ; ;"\\`NNTP: Connection closed\\.\\'" ; ;; info ; "\\`Node has no Previous\\'" ; "\\`No \".*\" in index\\'" ; ;; imenu ; ;"\\`No items suitable for an index found in this buffer\\.\\'" ; ;"\\`The mode \".*\" does not take full advantage of imenu\\.el yet\\.\\'" ; ;; ispell ; "\\`No word found to check!\\'" ; ;; man ; "\\`.* not found\\'" ; "\\`No more history\\.\\'" ; ;; etags ; "\\`File .* is not a valid tag table\\'" ; "\\`File .* is not a valid tags file\\'" ; "\\`All files processed\\.\\'" ; "No TAGS file name supplied\\'" ; "\\`Nothing to complete\\'" ; ;; BBDB ; "\\`no previous record\\'" ; "\\`no next record\\'")) (make-variable-buffer-local 'indent-tabs-mode) ;;; Load in generated autoloads (made by autoload.el). ;; (let ((dir load-path) ;; purify-flag) ;; (while dir ;; (condition-case nil ;; (load (concat (car dir) "auto-autoloads")) ;; (t nil)) ;; (pop dir))) ;;; Local Variables: ;;; no-byte-compile: t ;;; no-update-autoloads: t ;;; End: ;;; loaddefs.el ends here