From: Dave Love <d.love@dl.ac.uk>
Cc: emacs-unicode@gnu.org, emacs-devel@gnu.org, emacs-bidi@gnu.org,
Kenichi Handa <handa@m17n.org>
Subject: Re: synchronizing emacs-unicode branch to HEAD
Date: Tue, 09 Sep 2003 20:02:53 +0100 [thread overview]
Message-ID: <rzq8yoxrdia.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: jebrtuqo40.fsf@sykes.suse.de
Andreas Schwab <schwab@suse.de> writes:
> I'm getting a crash on ia64 during bootstrap while the lisp files are
> compiled. I can fix it with the patch below, but it is probably not the
> right fix. I guess one of the c_functions is not GC clean, but I haven't
> been able to find out which one.
That looks the right sort of fix to me at a quick glance. There's
clearly a gcpro missing somewhere. Mapping over keymaps might cause
autoloading as a possible source of GC.
However, I'm surprised it worked at all. The head code hasn't built
for some time on any of the three 64-bit systems I have (Solaris,
Irix, Tru64 -- I don't have 64-bit userland installed on Debian
sparc). This is apparently due to GC changes. It isn't a gcpro
issue, anyway. I'd hoped someone with an interest in ia64 would fix
it :-(.
Why not sort out conservative marking on ia64, by the way? See
comments probably in alloc.c and s/gnu-linux.h.
[This is one of the things that would just fall out of using the Boehm
collector, and I'm sure effort would be better spent on making that
work than messing with the current GC.]
next prev parent reply other threads:[~2003-09-09 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 23:32 synchronizing emacs-unicode branch to HEAD Kenichi Handa
2003-09-09 9:59 ` Andreas Schwab
2003-09-09 12:12 ` Kenichi Handa
2003-09-09 12:44 ` Andreas Schwab
2003-09-16 2:27 ` Kenichi Handa
2003-09-09 19:04 ` Dave Love
2003-09-09 19:02 ` Dave Love [this message]
2003-09-09 19:51 ` Andreas Schwab
2003-09-09 20:32 ` Miles Bader
2003-09-10 1:15 ` Kenichi Handa
2003-09-10 2:25 ` Miles Bader
2003-09-11 9:21 ` Dave Love
2003-09-11 18:28 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rzq8yoxrdia.fsf@albion.dl.ac.uk \
--to=d.love@dl.ac.uk \
--cc=emacs-bidi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-unicode@gnu.org \
--cc=handa@m17n.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).