public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* Platforms using COFF?
@ 2010-08-06  8:29 Eli Zaretskii
  2010-08-06 18:21 ` Michael Snyder
  0 siblings, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2010-08-06  8:29 UTC (permalink / raw)
  To: gdb

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.

TIA

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2010-08-07 14:29 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-08-06  8:29 Platforms using COFF? Eli Zaretskii
2010-08-06 18:21 ` Michael Snyder
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

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).