Mercurial > hg > xemacs-beta
annotate lisp/mode-motion.el @ 5157:1fae11d56ad2
redo memory-usage mechanism, add way of dynamically initializing Lisp objects
-------------------- ChangeLog entries follow: --------------------
lisp/ChangeLog addition:
2010-03-18 Ben Wing <ben@xemacs.org>
* diagnose.el (show-memory-usage):
Rewrite to take into account API changes in memory-usage functions.
src/ChangeLog addition:
2010-03-18 Ben Wing <ben@xemacs.org>
* alloc.c:
* alloc.c (disksave_object_finalization_1):
* alloc.c (lisp_object_storage_size):
* alloc.c (listu):
* alloc.c (listn):
* alloc.c (Fobject_memory_usage_stats):
* alloc.c (compute_memusage_stats_length):
* alloc.c (Fobject_memory_usage):
* alloc.c (Ftotal_object_memory_usage):
* alloc.c (malloced_storage_size):
* alloc.c (common_init_alloc_early):
* alloc.c (reinit_alloc_objects_early):
* alloc.c (reinit_alloc_early):
* alloc.c (init_alloc_once_early):
* alloc.c (syms_of_alloc):
* alloc.c (reinit_vars_of_alloc):
* buffer.c:
* buffer.c (struct buffer_stats):
* buffer.c (compute_buffer_text_usage):
* buffer.c (compute_buffer_usage):
* buffer.c (buffer_memory_usage):
* buffer.c (buffer_objects_create):
* buffer.c (syms_of_buffer):
* buffer.c (vars_of_buffer):
* console-impl.h (struct console_methods):
* dynarr.c (Dynarr_memory_usage):
* emacs.c (main_1):
* events.c (clear_event_resource):
* extents.c:
* extents.c (compute_buffer_extent_usage):
* extents.c (extent_objects_create):
* extents.h:
* faces.c:
* faces.c (compute_face_cachel_usage):
* faces.c (face_objects_create):
* faces.h:
* general-slots.h:
* glyphs.c:
* glyphs.c (compute_glyph_cachel_usage):
* glyphs.c (glyph_objects_create):
* glyphs.h:
* lisp.h:
* lisp.h (struct usage_stats):
* lrecord.h:
* lrecord.h (enum lrecord_type):
* lrecord.h (struct lrecord_implementation):
* lrecord.h (MC_ALLOC_CALL_FINALIZER_FOR_DISKSAVE):
* lrecord.h (DEFINE_DUMPABLE_LISP_OBJECT):
* lrecord.h (DEFINE_DUMPABLE_SIZABLE_LISP_OBJECT):
* lrecord.h (DEFINE_DUMPABLE_FROB_BLOCK_LISP_OBJECT):
* lrecord.h (DEFINE_DUMPABLE_FROB_BLOCK_SIZABLE_LISP_OBJECT):
* lrecord.h (DEFINE_DUMPABLE_INTERNAL_LISP_OBJECT):
* lrecord.h (DEFINE_DUMPABLE_SIZABLE_INTERNAL_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_SIZABLE_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_FROB_BLOCK_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_FROB_BLOCK_SIZABLE_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_INTERNAL_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_SIZABLE_INTERNAL_LISP_OBJECT):
* lrecord.h (MAKE_LISP_OBJECT):
* lrecord.h (DEFINE_DUMPABLE_MODULE_LISP_OBJECT):
* lrecord.h (DEFINE_DUMPABLE_MODULE_SIZABLE_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_MODULE_LISP_OBJECT):
* lrecord.h (DEFINE_NODUMP_MODULE_SIZABLE_LISP_OBJECT):
* lrecord.h (MAKE_MODULE_LISP_OBJECT):
* lrecord.h (INIT_LISP_OBJECT):
* lrecord.h (INIT_MODULE_LISP_OBJECT):
* lrecord.h (UNDEF_LISP_OBJECT):
* lrecord.h (UNDEF_MODULE_LISP_OBJECT):
* lrecord.h (DECLARE_LISP_OBJECT):
* lrecord.h (DECLARE_MODULE_API_LISP_OBJECT):
* lrecord.h (DECLARE_MODULE_LISP_OBJECT):
* lstream.c:
* lstream.c (syms_of_lstream):
* lstream.c (vars_of_lstream):
* marker.c:
* marker.c (compute_buffer_marker_usage):
* mc-alloc.c (mc_alloced_storage_size):
* mc-alloc.h:
* mule-charset.c:
* mule-charset.c (struct charset_stats):
* mule-charset.c (compute_charset_usage):
* mule-charset.c (charset_memory_usage):
* mule-charset.c (mule_charset_objects_create):
* mule-charset.c (syms_of_mule_charset):
* mule-charset.c (vars_of_mule_charset):
* redisplay.c:
* redisplay.c (compute_rune_dynarr_usage):
* redisplay.c (compute_display_block_dynarr_usage):
* redisplay.c (compute_glyph_block_dynarr_usage):
* redisplay.c (compute_display_line_dynarr_usage):
* redisplay.c (compute_line_start_cache_dynarr_usage):
* redisplay.h:
* scrollbar-gtk.c (gtk_compute_scrollbar_instance_usage):
* scrollbar-msw.c (mswindows_compute_scrollbar_instance_usage):
* scrollbar-x.c (x_compute_scrollbar_instance_usage):
* scrollbar.c (compute_scrollbar_instance_usage):
* scrollbar.h:
* symbols.c:
* symbols.c (reinit_symbol_objects_early):
* symbols.c (init_symbols_once_early):
* symbols.c (reinit_symbols_early):
* symbols.c (defsymbol_massage_name_1):
* symsinit.h:
* ui-gtk.c:
* ui-gtk.c (emacs_gtk_object_getprop):
* ui-gtk.c (emacs_gtk_object_putprop):
* ui-gtk.c (ui_gtk_objects_create):
* unicode.c (compute_from_unicode_table_size_1):
* unicode.c (compute_to_unicode_table_size_1):
* unicode.c (compute_from_unicode_table_size):
* unicode.c (compute_to_unicode_table_size):
* window.c:
* window.c (struct window_stats):
* window.c (compute_window_mirror_usage):
* window.c (compute_window_usage):
* window.c (window_memory_usage):
* window.c (window_objects_create):
* window.c (syms_of_window):
* window.c (vars_of_window):
* window.h:
Redo memory-usage mechanism, make it general; add way of dynamically
initializing Lisp object types -- OBJECT_HAS_METHOD(), similar to
CONSOLE_HAS_METHOD().
(1) Create OBJECT_HAS_METHOD(), OBJECT_HAS_PROPERTY() etc. for
specifying that a Lisp object type has a particular method or
property. Call such methods with OBJECT_METH, MAYBE_OBJECT_METH,
OBJECT_METH_OR_GIVEN; retrieve properties with OBJECT_PROPERTY.
Methods that formerly required a DEFINE_*GENERAL_LISP_OBJECT() to
specify them (getprop, putprop, remprop, plist, disksave) now
instead use the dynamic-method mechanism. The main benefit of
this is that new methods or properties can be added without
requiring that the declaration statements of all existing methods
be modified. We have to make the `struct lrecord_implementation'
non-const, but I don't think this should have any effect on speed --
the only possible method that's really speed-critical is the
mark method, and we already extract those out into a separate
(non-const) array for increased cache locality.
Object methods need to be reinitialized after pdump, so we put
them in separate functions such as face_objects_create(),
extent_objects_create() and call them appropriately from emacs.c
The only current object property (`memusage_stats_list') that
objects can specify is a Lisp object and gets staticpro()ed so it
only needs to be set during dump time, but because it references
symbols that might not exist in a syms_of_() function, we
initialize it in vars_of_(). There is also an object property
(`num_extra_memusage_stats') that is automatically initialized based
on `memusage_stats_list'; we do that in reinit_vars_of_alloc(),
which is called after all vars_of_() functions are called.
`disksaver' method was renamed `disksave' to correspond with the
name normally given to the function (e.g. disksave_lstream()).
(2) Generalize the memory-usage mechanism in `buffer-memory-usage',
`window-memory-usage', `charset-memory-usage' into an object-type-
specific mechanism called by a single function
`object-memory-usage'. (Former function `object-memory-usage'
renamed to `total-object-memory-usage'). Generalize the mechanism
of different "slices" so that we can have different "classes" of
memory described and different "slices" onto each class; `t'
separates classes, `nil' separates slices. Currently we have
three classes defined: the memory of an object itself,
non-Lisp-object memory associated with the object (e.g. arrays or
dynarrs stored as fields in the object), and Lisp-object memory
associated with the object (other internal Lisp objects stored in
the object). This isn't completely finished yet and we might need
to further separate the "other internal Lisp objects" class into
two classes.
The memory-usage mechanism uses a `struct usage_stats' (renamed
from `struct overhead_stats') to describe a malloc-view onto a set
of allocated memory (listing how much was requested and various
types of overhead) and a more general `struct generic_usage_stats'
(with a `struct usage_stats' in it) to hold all statistics about
object memory. `struct generic_usage_stats' contains an array of
32 Bytecounts, which are statistics of unspecified semantics. The
intention is that individual types declare a corresponding struct
(e.g. `struct window_stats') with the same structure but with
specific fields in place of the array, corresponding to specific
statistics. The number of such statistics is an object property
computed from the list of tags (Lisp symbols describing the
statistics) stored in `memusage_stats_list'. The idea here is to
allow particular object types to customize the number and
semantics of the statistics where completely avoiding consing.
This doesn't matter so much yet, but the intention is to have the
memory usage of all objects computed at the end of GC, at the same
time as other statistics are currently computed. The values for
all statistics for a single type would be added up to compute
aggregate values for all objects of a specific type. To make this
efficient, we can't allow any memory allocation at all.
(3) Create some additional functions for creating lists that
specify the elements directly as args rather than indirectly through
an array: listn() (number of args given), listu() (list terminated
by Qunbound).
(4) Delete a bit of remaining unused C window_config stuff, also
unused lrecord_type_popup_data.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Thu, 18 Mar 2010 10:50:06 -0500 |
parents | 3ecd8885ac67 |
children | 308d34e9f07d |
rev | line source |
---|---|
428 | 1 ;;; mode-motion.el --- Mode-specific mouse-highlighting of text. |
2 | |
3 ;; Copyright (C) 1992, 1993, 1997 Free Software Foundation, Inc. | |
4 | |
5 ;; Maintainer: XEmacs Development Team | |
6 ;; Keywords: internal, mouse, dumped | |
7 | |
8 ;; This file is part of XEmacs. | |
9 | |
10 ;; XEmacs is free software; you can redistribute it and/or modify it | |
11 ;; under the terms of the GNU General Public License as published by | |
12 ;; the Free Software Foundation; either version 2, or (at your option) | |
13 ;; any later version. | |
14 | |
15 ;; XEmacs is distributed in the hope that it will be useful, but | |
16 ;; WITHOUT ANY WARRANTY; without even the implied warranty of | |
17 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | |
18 ;; General Public License for more details. | |
19 | |
20 ;; You should have received a copy of the GNU General Public License | |
21 ;; along with XEmacs; see the file COPYING. If not, write to the | |
22 ;; Free Software Foundation, 59 Temple Place - Suite 330, | |
23 ;; Boston, MA 02111-1307, USA. | |
24 | |
25 ;;; Synched up with: Not in FSF. | |
26 | |
27 ;;; Commentary: | |
28 | |
29 ;; This file is dumped with XEmacs (when window system support is compiled in). | |
30 | |
31 ;;; Code: | |
32 | |
33 (defvar mode-motion-hook nil | |
34 "Function or functions which are called whenever the mouse moves. | |
35 Each function must take a single argument of the motion event. | |
36 You should normally use this rather than `mouse-motion-handler', which | |
37 does some additional window-system-dependent things. This hook is local | |
38 to every buffer, and should normally be set up by major-modes which want | |
39 to use special highlighting. Every time the mouse moves over a window, | |
40 the mode-motion-hook of the buffer of that window is run.") | |
41 | |
42 (make-variable-buffer-local 'mode-motion-hook) | |
43 | |
44 (defvar mode-motion-extent nil) | |
45 (make-variable-buffer-local 'mode-motion-extent) | |
46 | |
47 (defvar mode-motion-help-echo-string nil | |
48 "String to be added as the 'help-echo property of the mode-motion extent. | |
49 In order for this to work, you need to add the hook function | |
50 `mode-motion-add-help-echo' to the mode-motion hook. If this is a function, | |
51 it will be called with one argument (the event) and should return a string | |
52 to be added. This variable is local to every buffer.") | |
53 (make-variable-buffer-local 'mode-motion-help-echo-string) | |
54 | |
55 (defun mode-motion-ensure-extent-ok (event) | |
56 (let ((buffer (event-buffer event))) | |
57 (if (and (extent-live-p mode-motion-extent) | |
58 (eq buffer (extent-object mode-motion-extent))) | |
59 nil | |
60 (setq mode-motion-extent (make-extent nil nil buffer)) | |
61 (set-extent-property mode-motion-extent 'mouse-face 'highlight)))) | |
62 | |
63 (defun mode-motion-highlight-internal (event backward forward) | |
64 (let* ((buffer (event-buffer event)) | |
65 (point (and buffer (event-point event)))) | |
66 (if (and buffer | |
67 (not (eq buffer mouse-grabbed-buffer))) | |
68 ;; #### ack!! Too many calls to save-window-excursion / | |
69 ;; save-excursion (x-track-pointer calls, so does | |
70 ;; minibuf-mouse-tracker ...) This needs to be looked | |
71 ;; into. It's complicated by the fact that sometimes | |
72 ;; a mode-motion-hook might really want to change | |
73 ;; the point. | |
74 ;; | |
75 ;; #### The save-excursion must come before the | |
76 ;; save-window-excursion in order to function properly. I | |
77 ;; haven't given this much thought. Is it a bug that this | |
78 ;; ordering is necessary or is it correct behavior? | |
79 (save-excursion | |
80 (save-window-excursion | |
81 (set-buffer buffer) | |
82 (mode-motion-ensure-extent-ok event) | |
83 (if point | |
84 ;; Use save-excursion here to avoid | |
85 ;; save-window-excursion seeing a change in | |
86 ;; window point's value which would make the | |
87 ;; display code do a whole lot of useless work | |
88 ;; and making the display flicker horribly. | |
89 (save-excursion | |
90 (goto-char point) | |
91 (condition-case nil (funcall backward) (error nil)) | |
92 (setq point (point)) | |
93 (condition-case nil (funcall forward) (error nil)) | |
94 (if (eq point (point)) | |
95 (detach-extent mode-motion-extent) | |
96 (set-extent-endpoints mode-motion-extent point (point)))) | |
97 ;; not over text; zero the extent. | |
98 (detach-extent mode-motion-extent))))))) | |
99 | |
100 (defun mode-motion-highlight-line (event) | |
101 "For use as the value of `mode-motion-hook' -- highlight line under mouse." | |
102 (mode-motion-highlight-internal event 'beginning-of-line 'end-of-line)) | |
103 | |
104 (defun mode-motion-highlight-word (event) | |
105 "For use as the value of `mode-motion-hook' -- highlight word under mouse." | |
106 (mode-motion-highlight-internal | |
107 event | |
108 #'(lambda () (default-mouse-track-beginning-of-word nil)) | |
109 #'(lambda () (default-mouse-track-end-of-word nil)))) | |
110 | |
111 (defun mode-motion-highlight-symbol (event) | |
112 "For use as the value of `mode-motion-hook' -- highlight symbol under mouse." | |
113 (mode-motion-highlight-internal | |
114 event | |
115 #'(lambda () (default-mouse-track-beginning-of-word t)) | |
116 #'(lambda () (default-mouse-track-end-of-word t)))) | |
117 | |
118 (defun mode-motion-highlight-sexp (event) | |
119 "For use as the value of `mode-motion-hook' -- highlight form under mouse." | |
120 (mode-motion-highlight-internal | |
121 event | |
122 #'(lambda () | |
123 (if (= (char-syntax (following-char)) ?\() | |
124 nil | |
125 (goto-char (scan-sexps (point) -1)))) | |
126 #'(lambda () | |
127 (if (= (char-syntax (following-char)) ?\)) | |
128 (forward-char 1)) | |
129 (goto-char (scan-sexps (point) 1))))) | |
130 | |
131 (defun mode-motion-add-help-echo (event) | |
132 "For use as the value of `mode-motion-hook' -- add a 'help-echo property. | |
133 This causes the string in the 'help-echo property to be displayed when the | |
134 mouse moves over the extent. See `mode-motion-help-echo-string' for | |
135 documentation on how to control the string that is added." | |
136 (mode-motion-ensure-extent-ok event) | |
137 (let ((string (cond ((null mode-motion-help-echo-string) nil) | |
138 ((stringp mode-motion-help-echo-string) | |
139 mode-motion-help-echo-string) | |
140 (t (funcall mode-motion-help-echo-string event))))) | |
141 (if (stringp string) | |
142 (set-extent-property mode-motion-extent 'help-echo string)))) | |
143 | |
144 | |
145 (provide 'mode-motion) | |
146 | |
147 ;;; mode-motion.el ends here |