From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Platforms using COFF?
Date: Fri, 06 Aug 2010 18:21:00 -0000 [thread overview]
Message-ID: <4C5C528B.6000304@vmware.com> (raw)
In-Reply-To: <83lj8kw3ep.fsf@gnu.org>
Eli Zaretskii wrote:
> I'm sorry for posting a slightly off-topic question, but I think this
> forum has many people who know about what I'd like to ask: are there
> any current or future platforms that use, or can be reasonably
> expected to use, the COFF format for their binary files?
>
> Background: Emacs has a bunch of implementation of unexec, one each
> for every ABI used by platforms that Emacs can be built on. (unexec
> is a method of generating an executable binary file from an in-memory
> image of a running program.) There are, for example, unexelf.c for
> ELF, unexw32.c for pe-coff, etc. There's also unexcoff.c (renamed
> yesterday from unexec.c), which was the original implementation
> supporting a.out and COFF. Nowadays, it is used only by the MSDOS
> (a.k.a. DJGPP) build of Emacs.
>
> The main issue is this: since only the MSDOS build uses unexcoff.c, I
> was asked to clean it up of code that is #ifdef'ed away for the DOS
> build. My question is: can we reasonably assume that no future
> platform where it makes sense to build Emacs will ever want to use
> COFF? If some modern low-end platforms (e.g., some mobile ones) use
> or could use COFF, then perhaps some of the code currently unused by
> the DOS build should be left in unexcoff.c, for the benefit of these
> platforms.
Not sure how meaningful, but...
grep -li coff config/*/*
config/djgpp/fnchange.lst
config/powerpc/aix.mh
config/rs6000/nm-rs6000.h
next prev parent reply other threads:[~2010-08-06 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 8:29 Eli Zaretskii
2010-08-06 18:21 ` Michael Snyder [this message]
2010-08-07 9:16 ` Eli Zaretskii
2010-08-07 13:06 ` Daniel Jacobowitz
2010-08-07 13:24 ` Mark Kettenis
2010-08-07 14:04 ` Eli Zaretskii
2010-08-07 14:29 ` Mark Kettenis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C5C528B.6000304@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.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.
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).