[gmane.emacs.devel] Re: list-matching-lines is alias for occur
19 years
Adrian Aichner
Adrian Aichner
Is this where the lost M-x list-matching-lines in recent occur.el
comes from?
Adrian
- 1 participants
- 0 comments
[Failure] XEmacs 21.5-b23 "daikon" (+CVS-20051101) i586-pc-win32
19 years
Adrian Aichner
Adrian Aichner
Marcus, using this
and this small patch:
--- c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src\mc-alloc.c.orig 2005-11-07 22:25:29.952375000 +0100
+++ c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src\mc-alloc.c 2005-11-07 22:14:12.436750000 +0100
＠＠ -831,7 +831,7 ＠＠
free_page_header (page_header *ph)
{
#ifdef BLOCKTYPE_ALLOC_PAGE_HEADER
- return Blocktype_free (the_page_header_blocktype, ph);
+ Blocktype_free (the_page_header_blocktype, ph);
#else /* not BLOCKTYPE_ALLOC_PAGE_HEADER */
#if ZERO_MEM
ZERO_PAGE_HEADER (ph);
I get a bit farther:
elhash.c
c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src\elhash.c(423) : error C2065: 'size' : undeclared identifier
NMAKE: fatal error U1077: 'cl' : return code '0x2'
Stop.
Compilation exited abnormally with code 2 at Mon Nov 07 22:15:53
You must have tested with ERROR_CHECK_STRUCTURES only?
Adrian
> XEmacs Build Report generated by emacs-version
> 21.5 (beta23) "daikon" (+CVS-20051031) XEmacs Lucid
> with system-configuration
> i586-pc-win32
> follows:
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\Installation:
> (Output from most recent run of ./configure)
OS version:
Microsoft Windows XP [Version 5.1.2600]
OS: Windows_NT
XEmacs 21.5-b23 "daikon" (+CVS-20051101) configured for `i586-pc-win32'.
Building XEmacs using "NMAKE".
Building XEmacs using make flags " ".
Building XEmacs in source tree "c:\\Hacking\\cvs.xemacs.org\\XEmacs\\xemacs-21.5-clean".
For src, using compiler "cl -nologo -W3 -DSTRICT -Zi -Od -MDd -c -TP -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\inc -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src -I"c:\Hacking\libs4xemacs\xpm-3.4k" -I"c:\Hacking\libs4xemacs\xpm-3.4k\lib" -I"c:\Hacking\libs4xemacs\libpng-1.0.2" -I"c:\Hacking\libs4xemacs\zlib" -I"c:\Hacking\libs4xemacs\tiff-v3.4\libtiff" -I"c:\Hacking\libs4xemacs\jpeg-6b" -I"c:\Hacking\libs4xemacs\compface" -I"c:\Hacking\libs4xemacs\zlib" -DHAVE_MS_WINDOWS -DHAVE_MENUBARS -DHAVE_SCROLLBARS -DHAVE_TOOLBARS -DHAVE_WIDGETS -DHAVE_DIALOGS -DHAVE_XPM -DFOR_MSW -DHAVE_GIF -DHAVE_PNG -DHAVE_TIFF -DHAVE_JPEG -DHAVE_XFACE -DHAVE_ZLIB -DHAVE_NATIVE_SOUND -DMULE -DPDUMP -DNEW_GC -DUSE_KKCC -DMC_ALLOC -DSYSTEM_MALLOC -DDEBUG_XEMACS -D_DEBUG -DWIN32_LEAN_AND_MEAN -DWIN32_NATIVE -Demacs -DHAVE_CONFIG_H -DPATH_VERSION=\"21.5-b23\" -DPATH_PROGNAME=\"xemacs\" -DEMACS_VERSION=\"21.5-b23\" -DEMACS_PROGNAME=\"xemacs\" -DSTACK_TRACE_EYE_CATCHER=xemacs_21_5_b23_i586_pc_win32 -DPATH_PREFIX=\"..\" -DEMACS_MAJOR_VERSION=21 -DEMACS_MINOR_VERSION=5 -DEMACS_BETA_VERSION=23 -DXEMACS_CODENAME=\""daikon"\" -DXEMACS_EXTRA_NAME=\"(+CVS-20051101)\" -DEMACS_CONFIGURATION=\"i586-pc-win32\" -DPATH_PACKAGEPATH=\""~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages"\"".
For lib-src, using compiler "cl -nologo -W3 -DSTRICT -Zi -Od -MDd -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lib-src -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src -DHAVE_CONFIG_H -DWIN32_NATIVE".
Compiling as C++.
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b23".
Package path is "~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in international (MULE) support.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for X-Face message headers.
Compiling in support for GZIP compression/decompression.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library.
Compiling in debugging support (no slowdown).
Using new experimental GC algorithms.
Using new experimental allocator.
Using new experimental incremental garbage collector.
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\xemacs-21.5-clean-cvs-update.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\
Compilation started at Wed Nov 02 19:16:34 2005 +0100 (W. Europe Standard Time)
? gunzip-error.txt
? man/lispref/errors.texi.new
? nt/xemacs-21.5-clean-make-all-texinfo-error.err
P version.sh
rcsmerge: warning: conflicts during merge
C lisp/ChangeLog
M lisp/cmdloop.el
P lisp/diagnose.el
M lisp/package-get.el
P modules/ChangeLog
U modules/canna/.cvsignore
P src/ChangeLog
M src/frame-msw.c
P src/realpath.c
cvs server: Updating tests
cvs server: Updating tests/DLL
M tests/automated/region-tests.el
U lisp/diagnose.el
U src/realpath.c
Compilation finished at Wed Nov 02 19:18:09
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-all.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\
nmake /f xemacs.mak all
Compilation started at Mon Nov 07 22:15:24 2005 +0100 (W. Europe Standard Time)
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b23".
1 file(s) copied.
1 File(s) copied
1 File(s) copied
c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src\elhash.c(423) : error C2065: 'size' : undeclared identifier
NMAKE: fatal error U1077: 'cl' : return code '0x2'
Compilation exited abnormally with code 2 at Mon Nov 07 22:15:53
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-check-temacs.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\
nmake /f xemacs.mak check-temacs
Compilation started at Wed Nov 02 19:59:09 2005 +0100 (W. Europe Standard Time)
Using load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\)
Using module-load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\modules)
base64-tests.el: 1234 of 1234 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
byte-compiler-tests.el: 66 of 66 tests successful (100%).
38 tests skipped because can't defadvice.
0 errors that should have been generated, but weren't
0 wrong-error failures
c-tests.el: 4 of 4 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
case-tests.el: 1148 of 1148 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
ccl-tests.el: 4570 of 4570 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
database-tests.el: No tests run.
0 errors that should have been generated, but weren't
0 wrong-error failures
extent-tests.el: 194 of 194 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
hash-table-tests.el: 9866 of 9866 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
lisp-tests.el: 3672 of 3672 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
md5-tests.el: 56 of 56 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
mule-tests.el: 232 of 236 tests successful ( 98%).
0 errors that should have been generated, but weren't
0 wrong-error failures
Unexpected error (void-function executable-find) while executing interpreted code.
Unexpected error (void-function executable-find) while executing byte-compiled code.
os-tests.el: No tests run.
Unexpected error (void-function executable-find) while executing interpreted code
Unexpected error (void-function executable-find) while executing byte-compiled code
0 errors that should have been generated, but weren't
0 wrong-error failures
regexp-tests.el: 350 of 350 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests-1-1.el: 28 of 28 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests.el: 38 of 38 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
symbol-tests.el: 246 of 246 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
syntax-tests.el: 56 of 56 tests successful (100%).
2 tests skipped because c-mode unavailable.
0 errors that should have been generated, but weren't
0 wrong-error failures
tag-tests.el: 6 of 6 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
weak-tests.el: 140 of 140 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
base64-tests.el: 1234 of 1234 tests successful (100%).
byte-compiler-tests.el: 66 of 66 tests successful (100%).
c-tests.el: 4 of 4 tests successful (100%).
case-tests.el: 1148 of 1148 tests successful (100%).
ccl-tests.el: 4570 of 4570 tests successful (100%).
database-tests.el: No tests run.
extent-tests.el: 194 of 194 tests successful (100%).
hash-table-tests.el: 9866 of 9866 tests successful (100%).
lisp-tests.el: 3672 of 3672 tests successful (100%).
md5-tests.el: 56 of 56 tests successful (100%).
mule-tests.el: 232 of 236 tests successful ( 98%).
os-tests.el: No tests run.
regexp-tests.el: 350 of 350 tests successful (100%).
region-tests-1-1.el: 28 of 28 tests successful (100%).
region-tests.el: 38 of 38 tests successful (100%).
symbol-tests.el: 246 of 246 tests successful (100%).
syntax-tests.el: 56 of 56 tests successful (100%).
tag-tests.el: 6 of 6 tests successful (100%).
weak-tests.el: 140 of 140 tests successful (100%).
Compilation finished at Wed Nov 02 19:59:19
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-check.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\
nmake /f xemacs.mak check
Compilation started at Wed Nov 02 19:59:30 2005 +0100 (W. Europe Standard Time)
base64-tests.el: 1234 of 1234 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
byte-compiler-tests.el: 104 of 104 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
c-tests.el: 4 of 4 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
case-tests.el: 1148 of 1148 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
ccl-tests.el: 4570 of 4570 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
database-tests.el: No tests run.
0 errors that should have been generated, but weren't
0 wrong-error failures
extent-tests.el: 194 of 194 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
hash-table-tests.el: 9866 of 9866 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
lisp-tests.el: 3672 of 3672 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
md5-tests.el: 56 of 56 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
mule-tests.el: 232 of 236 tests successful ( 98%).
0 errors that should have been generated, but weren't
0 wrong-error failures
os-tests.el: 20 of 20 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
regexp-tests.el: 350 of 350 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests-1-1.el: 28 of 28 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests.el: 38 of 38 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
symbol-tests.el: 246 of 246 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
syntax-tests.el: 60 of 60 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
tag-tests.el: 6 of 6 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
weak-tests.el: 140 of 140 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
base64-tests.el: 1234 of 1234 tests successful (100%).
byte-compiler-tests.el: 104 of 104 tests successful (100%).
c-tests.el: 4 of 4 tests successful (100%).
case-tests.el: 1148 of 1148 tests successful (100%).
ccl-tests.el: 4570 of 4570 tests successful (100%).
database-tests.el: No tests run.
extent-tests.el: 194 of 194 tests successful (100%).
hash-table-tests.el: 9866 of 9866 tests successful (100%).
lisp-tests.el: 3672 of 3672 tests successful (100%).
md5-tests.el: 56 of 56 tests successful (100%).
mule-tests.el: 232 of 236 tests successful ( 98%).
os-tests.el: 20 of 20 tests successful (100%).
regexp-tests.el: 350 of 350 tests successful (100%).
region-tests-1-1.el: 28 of 28 tests successful (100%).
region-tests.el: 38 of 38 tests successful (100%).
symbol-tests.el: 246 of 246 tests successful (100%).
syntax-tests.el: 60 of 60 tests successful (100%).
tag-tests.el: 6 of 6 tests successful (100%).
weak-tests.el: 140 of 140 tests successful (100%).
Compilation finished at Wed Nov 02 19:59:41
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
- 3 participants
- 5 comments
sarcasm, charsets, unicode-internal and all that jazz
19 years
Ben Wing
Ben Wing
i've gotten to the point in unicode-internal where it compiles, builds
and dumps. then it proceeds to hang upon pdump load. when compiling
without kkcc and without mc-alloc, it gets stuck in loadup, loading
european.el. in this case it's not wedged so much as just extremely
slow due to the continual syntax-mirror updating. this is something
that's likely to be a classic case of premature optimization; the mirror
table is trying to save a few cycles in the retrieval of a syntax code
from a char table, but it takes a very long time to compute, and had no
smarts for handling lots of updates, one after the other. i'm just
planning on turning on the mirror table code and not worry about things,
only worrying once the C-profiling outputs show that there really is a
bottleneck here. (we really need a lot more profiling. that's something
any of you (stephen or otherwise) could do if you have a chance.
remember to profile with a complete, full-on release build -- no
error-checking, lots of optimization, etc. make sure to do C profiling,
not just Lisp profiling, since that'll tell us where the real slowness
is. actually, what would be real cool is for one of you to do this and
then *write down* *exactly* the steps needed to reproduce the profiling
session, in great detail -- not knowing how to do it is what has tended
to defer my attempts at profiling. also, if you use any sort of
framework to drive the profiling and collect data over various
performance sets, please include that framework.
ben
- 1 participants
- 1 comments
changing the values of iso-8859-* charsets
19 years
Ben Wing
Ben Wing
i am 99% of the way towards beginning to try to compile unicode-internal :)
currently we use 32-127 for the values of the chars in the iso-8859
charsets. maybe that was needed under old-mule, but in unicode-internal
charsets can have values in any arbitrary interval or rectangle in 256
or 256x256 space. shouldn't we use 160-255? this would only matter in
the output of `split-char'; `make-char' already goes either way.
ben
- 3 participants
- 23 comments
[Success] XEmacs 21.5-b23 "daikon" i686-pc-linux
19 years
Joachim Schrod
Joachim Schrod
Hi,
I wanted to get daikon, got adventurous, and used Build (for the first
time ;-) on my shiny new SUSE 10.0 installation. (SUSE 10.0 comes with
XEmacs corn, supplied by Mike Fabian).
That was successful overall, but with a few annoyances.
XEmacs did not select any optimization flags. According to the
explanation in Build (and about --with-cflags-optimization in INSTALL)
they should be selected automatically. Does this mean that no
optimization can be used at a straight forward SUSE system? (I cannot
believe that.)
Other annoyances were caused by Build that was delivered with SUSE's
XEmacs: efs is not loaded by default, it could not save the build
configuration, the build output collection didn't work at all and had
to be done manually by me. (Btw, I started xemacs with -q to avoid
inference with any personal startup files.)
I will now retry, and rebuild daikon from within that newly built
daikon with the current sumo packages installed -- and with
optimization enabled this time... I'll check if Build works better
from there. Shall I send a build report from that as well?
Best,
Joachim
> XEmacs Build Report generated by emacs-version
> 21.5 (beta21) "corn" (+CVS-20050720) XEmacs Lucid
> with system-configuration
> i386-suse-linux
> follows:
> Contents of /home/schrod/src/xemacs/xemacs-r21-5-current-beta/Installation:
> (Output from most recent run of ./configure)
uname -a: Linux n-pussy 2.6.13-15-smp #1 SMP Tue Sep 13 14:56:15 UTC 2005 i686 i686 i386 GNU/Linux
configure '--prefix=/opt/xemacs'
XEmacs 21.5-b23 "daikon" configured for `i686-pc-linux'.
Compilation Environment and Installation Defaults:
Source code location: /home/schrod/src/xemacs/xemacs-r21-5-current-beta
Installation prefix: /opt/xemacs
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler version: gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux)
- GCC specs file: specs.
- Compiler command: gcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wunused-parameter -g
libc version: 2.3.5
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11/include
- X Windows libraries location: /usr/X11/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw
- Athena library to link: Xaw
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Sound:
Compiling in support for sound (native).
Databases:
Internationalization:
Mail:
Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new GC algorithms.
WARNING: ---------------------------------------------------------
WARNING: The new algorithms are experimental. They are enabled by
WARNING: default for this release. Use `--disable-kkcc' to
WARNING: turn it off.
WARNING: ---------------------------------------------------------
Using the new allocator.
WARNING: ---------------------------------------------------------
WARNING: The new allocator is experimental. It is enabled by
WARNING: default for this release. Use `--disable-mc-alloc' to
WARNING: turn it off.
WARNING: ---------------------------------------------------------
Using the new portable dumper.
Compiling in support for extra debugging code.
Compiling in support for runtime error checking.
WARNING: ---------------------------------------------------------
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
> Contents of /home/schrod/src/xemacs/xemacs-r21-5-current-beta/beta.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* \|^\(FAIL\|SKIP\):"
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:\|^\s-*0 .*\(failure\|error\)s?\|^PASS:\|(100%) tests successful"
cd /home/schrod/src/xemacs/xemacs-r21-5-current-beta/
Compilation started at Wed Nov 2 12:35:44 2005 +0100 (CET)
checking for preferred warning flags for XEMACS_CC... -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wunused-parameter
checking for preferred warning flags for CC... -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes
checking for dlerror... yes
checking for _dlerror... no
checking for perror... yes
checking for strerror... yes
Compilation Environment and Installation Defaults:
Compiling in support for runtime error checking.
Compilation finished at Wed Nov 2 12:36:25
> Contents of /home/schrod/src/xemacs/xemacs-r21-5-current-beta/xemacs-make-all.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* \|^\(FAIL\|SKIP\):"
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:\|^\s-*0 .*\(failure\|error\)s?\|^PASS:\|(100%) tests successful"
cd /home/schrod/src/xemacs/xemacs-r21-5-current-beta/
make
Compilation started at Wed Nov 2 12:38:27 2005 +0100 (CET)
cd ./lib-src && make all
cd ./lwlib && make all
xlwradio.c:253: warning: 'RadioDestroy' defined but not used
xlwcheckbox.c:292: warning: 'CheckboxDestroy' defined but not used
xlwgauge.c:841: warning: missing sentinel in function call
cd ./src && make all
realpath.c:83: warning: unused parameter 'links_only'
frame-x.c:770: warning: missing sentinel in function call
frame-x.c:775: warning: missing sentinel in function call
frame-x.c:874: warning: missing sentinel in function call
Using load-path (/home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/)
Using module-load-path (/home/schrod/src/xemacs/xemacs-r21-5-current-beta/modules)
Generating autoloads for lisp/next-error.el...
While compiling the end of the data in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/obsolete.el:
** The following functions are not known to be defined:
charsets-in-string, charsets-in-region
While compiling the end of the data in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/faces.el:
** The following functions are not known to be defined: charsetp,
find-charset
While compiling describe-register-1 in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/register.el:
** reference to free variable yank-excluded-properties
While compiling the end of the data:
** the function remove-list-of-text-properties is not known to be defined.
While compiling the end of the data in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/diagnose.el:
** The following functions are not known to be defined:
sort-numeric-fields, lrecord-stats
While compiling get-selection in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/select.el:
** variable err bound but not referenced
While compiling forward-paragraph in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/paragraphs.el:
** variable multiple-lines bound but not referenced
While compiling the end of the data:
** the function constrain-to-field is not known to be defined.
Using load-path (/home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/)
Using module-load-path (/home/schrod/src/xemacs/xemacs-r21-5-current-beta/modules)
Requiring next-error...
While compiling multi-occur in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/occur.el:
** variable ido-ignore-item-temp-list bound but not referenced
** misplaced interactive spec: (interactive (cons (let* ((bufs (list (read-buffer "First buffer to search: " (current-buffer) t))) (buf nil) (ido-ignore-item-temp-list bufs)) (while (not (string-equal (setq buf (read-buffer (if (and-boundp (quote read-buffer-function) (quote (eq read-buffer-function (quote ido-read-buffer)))) "Next buffer to search (C-j to end): " "Next buffer to search (RET to end): ") nil t)) "")) (add-to-list (quote bufs) buf) (setq ido-ignore-item-temp-list bufs)) (nreverse (mapcar (function get-buffer) bufs))) (occur-read-primary-args)))
While compiling occur-engine:
** reference to free variable jit-lock-mode
While compiling the end of the data:
** the function jit-lock-fontify-now is not known to be defined.
Compiling /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/next-error.el...
Wrote /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/next-error.elc
While compiling the end of the data in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/msw-font-menu.el:
** The following functions are not known to be defined:
mswindows-parse-font-style, mswindows-construct-font-style
While compiling the end of the data in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/gtk.el:
** the function gtk-import-function is not known to be defined.
While compiling toplevel forms in file /home/schrod/src/xemacs/xemacs-r21-5-current-beta/lisp/gtk-iso8859-1.el:
** assignment to free variable character-set-property
Computing custom-loads for next-error...
cd /home/schrod/src/xemacs/xemacs-r21-5-current-beta/man && make info
Compilation finished at Wed Nov 2 12:40:59
> Contents of /home/schrod/src/xemacs/xemacs-r21-5-current-beta/xemacs-make-install.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* \|^\(FAIL\|SKIP\):"
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:\|^\s-*0 .*\(failure\|error\)s?\|^PASS:\|(100%) tests successful"
cd /home/schrod/src/xemacs/xemacs-r21-5-current-beta/
make install
Compilation started at Wed Nov 2 13:16:41 2005 +0100 (CET)
cd ./lib-src && make all
cd ./lwlib && make all
cd ./src && make all
cd /home/schrod/src/xemacs/xemacs-r21-5-current-beta/man && make info
cd ./src && make check-features
Installing utilities run internally by XEmacs.
Installing utilities for users to run.
cd /opt/xemacs/bin && rm -f ./xemacs && ln -s xemacs-21.5-b23 ./xemacs
cd /home/schrod/src/xemacs/xemacs-r21-5-current-beta/etc && \
make gzip-el
Compilation finished at Wed Nov 2 13:16:51
/home/schrod/src/xemacs/xemacs-r21-5-current-beta/xemacs-make-check.err not found!
/home/schrod/src/xemacs/xemacs-r21-5-current-beta/xemacs-make-check-temacs.err not found!
- 3 participants
- 5 comments
Re: [PATCH21.5] Incremental Garbage Collector
19 years
Ben Wing
Ben Wing
Marcus Crestani wrote:
>More information about the dynarr object: Dynamic arrays are
>extensively used for separately allocated objects. In the old garbage
>collector, dynamic arrays held non-Lisp objects as well as Lisp
>objects. The new incremental garbage collector distinguishes between
>dynamic arrays that hold Lisp objects and dynamic arrays that hold
>non-Lisp objects. For dynamic arrays that hold Lisp objects, I
>created the new Lisp object type "Dynamic Lisp Array," called
>dynarr_lisp. It contains Lisp objects, in contrast to the dynamic
>array dynarr that contains non-Lisp objects.
>
>For dynamic Lisp arrays, the allocator has to be extended: I added two
>more primitives to the new allocator to allow allocation of elements
>in a contiguous block of memory: mc_alloc_array and
>alloc_lrecord_array. Each element in the array is a regular Lisp
>object with its own Lisp object header and mark bit.
>
>
Marcus, does this mean it's possible to allocate an array of Lisp
Objects (i.e. pointers, not an array of actual objects themselves),
with a pointer to it from a Lisp Object, and have it handled properly by
kkcc/mc-alloc/new-gc? This would solve many of the problems of my char
table. ideally, this could work recursively -- you could allocate an
array of pointers to arrays of Lisp Objects and have new-gc and friends
handle this upper array as well. but even if i can do this just at the
lowest level, it will be a big win, since that's where most of the
subtables will occur. "handled properly by kkcc" means that kkcc
recognizes if it's seen this array before and doesn't retraverse it if so.
ben
- 3 participants
- 3 comments
21.5 Build/configure defaults
19 years
Joachim Schrod
Joachim Schrod
Hi,
IMHO, MULE should be on by default for 21.5.
Also, you don't need to answer my question on optimization flags for
SUSE any more. I detected --with-optimization in the mean time. (I
should have read configure.usage before INSTALL.)
Cheers, Joachim
- 3 participants
- 5 comments
kkcc exceeding slowness
19 years
Ben Wing
Ben Wing
unicode-internal now gets most of the way through the build process;
currently, it gets most of the way through autoload re-creation before
hitting a syntax error.
but in the process i've noticed that kkcc is *unbelievably* slow with
the new char tables i've designed. or at least i assume that's where
the slowness is; this is the only major change i've made to any
objects. without kkcc, gc is fast but with it, it rapidly balloons, to
the point where it takes 2 *minutes* or more to do a gc once all modules
are loaded.
the format of the char tables is something like a trie. a typical char
table for unicode has three levels. the top level is an array of 256
elements indexing bits 23-16 of a unicode char; each element points to
another array of 256 elements, indexing bits 15-8; each element of the
second level also points to an array of 256 elements, for bits 7-0,
whose values are Lisp objects. there will be a fourth level on top of
the other three if a unicode char of 0x1000000 or greater is seen. in
order to avoid a memory explosion, each place at which there are no
defined elements points to a shared "blank" table. hence, originally
the char table contains a single 256-element array, each of whose
elements points to the same empty table. when a value for a particular
character is added, the tables are expanded along that path.
because the mark method is a method, i can put logic into it to check to
see whether a blank table is being traversed and stop traversing at that
point. the problem seems to be that kkcc can't be told this, and isn't
smart enough (at least i don't think so) to recognize whether it's
already traversed something unless it's a Lisp object -- and the
subtables aren't Lisp objects. i could make them Lisp objects, but this
means either [1] i integrate the header and the table, leading to an
object whose size is slightly over a power of 2 and hence its allocation
is difficult to manage efficiently (i assume, at least -- marcus, how
does mc-alloc handle this case?); or [2] i separate them into two
objects, which doubles the number of memory accesses to look up a character.
which is the lesser of two evils?
ben
- 3 participants
- 3 comments
Re: [PATCH21.5] Incremental Garbage Collector
19 years
Ben Wing
Ben Wing
Marcus Crestani wrote:
>This patch introduces an incremental garbage collector for XEmacs.
>All changes to the code are conditioned on `NEW_GC'. To enable the
>new garbage collector, configure with `--enable-newgc'.
>
>
Marcus, this is awesome! thanks very much for all your work. i
especially appreciate the fact that you've done the work to get this
working on windows (and mac) as well as unix, provided appropriate
versions of gdbinit and such, and taken care of a lot of other little
details that really need to be done in order for this to become really
usable rather than just an "80%" research project tnat never's quite
ready for prime time. you also clearly understand the XEmacs code well
and have obviously been very careful in the way you've written and
tested your code.
i'll take a look at this more extensively later, but a few comments:
-- i think we should go ahead and remove the conditionalization on the
parts of your patch that convert internal structures to lisp objects.
it won't hurt to have the structures be lisp objects always, even with
the old gc, and it will make the code much simpler, as well as easier to
maintain
-- my biggest concern is with gc.c. you just copied a lot of stuff from
alloc.c, and this tends to lead to bit-rot. is there a way you could
conditionalize it so the functions that you need more or less unchanged
remain in alloc.c or are split out into some other file? go ahead and
put new code in gc.c, but duplicated code is bad bad bad as it leads to
bit-rot and maintenance headaches.
-- once you commit this code, i'll start working on stuff you missed,
like in file-coding.c/mule-coding.c, where you have non-Lisp struct
coding_stream, which contains a DATA pointer to a separate set of
instance data, one per type of coding system, which is also a non-Lisp
structure often with Lisp elements in it. I'd suggest reworking this to
follow the lead of the main coding-system and specifier objects, and
incorporate extra data as part of the object itself, making the object
stretchy. that reduces greatly the need to create new objects for each
new subtype, and simplifies creation of new subtypes. (I'd suggest doing
the same for frame, device, etc. for similar reasons, although that can
wait.)
-- since you are creating a lot of new internal objects, i'd suggest a
minor change to the semantics of the object print method. currently if
you set it to 0, if calls default_object_printer. for internal objects,
which should never escape to Lisp level, we want internal_object_printer
instead. currently, even looking among the modules, there is only one
object (toolbar-button) that relies on the current behavior by
specifying 0 to get default_object_printer, while a number of others
(the event-*-data objects -- granted, not currently used) also specify 0
but really want internal_object_printer. your new internal objects do
the same. so i'd suggest just changing things in print_internal() to
call internal_object_printer when there is no print method, and change
the print method for toolbar-button to default_object_printer.
overall, thank you very, very much for this work and for your continued
commitment to work on generational algorithms and other state-of-the-art
stuff!
ben
- 2 participants
- 1 comments
Warning while compiling Gnus
19 years
Nelson Ferreira
Nelson Ferreira
Hi all,
I get the following warning while compiling Gnus (everything works
fine nonetheless).
While loading fsf-compat, run-at-time was not fboundp. This
typically means your fsf-compat package is newer than xemacs-base.
You
should update your xemacs-base package.
I tracked it down to timer.el of the fsf-compat. This message is
definitely not true, since I am to the latest rev of the packages.
This small patch fixes it for me. I am not sure if it has any bad side
effects. Thoughts anyone ?
Thanks,
Nelson
cvs server: Diffing .
Index: timer.el
===================================================================
RCS file:
/pack/xemacscvs/XEmacs/packages/xemacs-packages/fsf-compat/timer.el,v
retrieving revision 1.4
diff -u -u -b -r1.4 timer.el
--- timer.el 2004/10/22 15:23:00 1.4
+++ timer.el 2005/11/08 05:42:58
＠＠ -28,10 +28,11 ＠＠
;;; Code:
-(unless (fboundp #'run-at-time)
+(eval-when '(load eval)
+ (unless (fboundp #'run-at-time)
(warn "While loading fsf-compat, run-at-time was not fboundp. This
typically means your fsf-compat package is newer than xemacs-base.
You
-should update your xemacs-base package."))
+should update your xemacs-base package.")))
(require 'itimer)
--
Nelson Ferreira
- 1 participants
- 0 comments