From: Camm Maguire <camm@enhanced.com>
Cc: 204789@bugs.debian.org, Daniel Jacobowitz <dan@debian.org>,
debian-ia64@lists.debian.org, 217484@bugs.debian.org,
gcl-devel@gnu.org, emacs-devel@gnu.org
Subject: Bug#204789: [Gcl-devel] Re: ia64 function descriptors and unexec
Date: 31 Oct 2003 11:06:06 -0500 [thread overview]
Message-ID: <54ekwtcryp.fsf@intech19.enhanced.com> (raw)
In-Reply-To: <jeptgfhh8s.fsf@sykes.suse.de>
Greetings!
Andreas Schwab <schwab@suse.de> writes:
> > Was there ever a GNU emacs obstacle on ia64 linux, or am I confusing
> > the situation with xemacs?
>
> Since GNU Emacs does not assign function pointers at runtime there was
> never such a problem.
>
Could you please sketch how this is accomplished in emacs, given its
lisp base? I.e. as one initializes the lisp when building emacs, does
one not create function objects containing pointers/function addresses
which are then dumped in the unexec? Or are all lisp function objects
statically defined in C source files as explicitly initialized
structures?
Take care,
> Andreas.
>
> --
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
> Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
>
>
--
Camm Maguire camm@enhanced.com
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
next prev parent reply other threads:[~2003-10-31 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1ADSmN-0007pE-00@intech19.enhanced.com>
[not found] ` <20031025183937.GB21046@nevyn.them.org>
[not found] ` <543cddb93x.fsf@intech19.enhanced.com>
[not found] ` <20031028165700.GA1308@nevyn.them.org>
2003-10-29 15:20 ` ia64 function descriptors and unexec Camm Maguire
2003-10-29 16:28 ` Andreas Schwab
2003-10-29 17:36 ` Camm Maguire
2003-10-29 21:21 ` [Gcl-devel] " Andreas Schwab
2003-10-29 22:55 ` Peter Chubb
2003-10-30 6:47 ` Bug#204789: " Stephen J. Turnbull
2003-10-30 9:22 ` Peter Chubb
2003-10-31 0:08 ` Bug#204789: " Richard Stallman
2003-10-31 16:06 ` Camm Maguire [this message]
2003-10-31 17:02 ` Andreas Schwab
2003-10-31 22:47 ` Bug#204789: " Camm Maguire
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=54ekwtcryp.fsf@intech19.enhanced.com \
--to=camm@enhanced.com \
--cc=204789@bugs.debian.org \
--cc=217484@bugs.debian.org \
--cc=dan@debian.org \
--cc=debian-ia64@lists.debian.org \
--cc=emacs-devel@gnu.org \
--cc=gcl-devel@gnu.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).