public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "David and Jannette Uczen" <uczen@mint.net>
To: <binutils@sourceware.cygnus.com>
Subject: ELF header machine types (e_machine)
Date: Thu, 14 Oct 1999 18:38:00 -0000	[thread overview]
Message-ID: <000f01bf16ad$d1148740$9181e3d8@duczen--lap.hannaford.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]

Hi, I am new to this mailing list, so forgive me 
if I am asking an age-old question.
 
I am an IBM-mainframer with an interest in GNU 
utilities (we have GCC for OS/390, for example) and Linux. Looking through the 
binutils-2.9.5.0.16 source code, I noticed that in /include/elf/common.h there 
are 2 definitions for the IBM System/370 (or S/390). One is EM_S370 (9), 
presumably used by Amdahl's UTS, a SVR4-variant for System/370-compatible 
systems, and the other is EM_I370 (0xF00F), presumably for Running Linux On the 
Mainframe (ROAM).
 
Questions:
1) Shouldn't there be one definition for an architecture? 
These two are essentially the same. The only different one _might_ be a new 
EM_S390 / EM_I390 for IBM's System/390 CMOS Microprocessor, while upwardly 
compatible with older System/370 processors, does have new unique features such 
as support for IEEE floating point. However, this scheme was done with Intel 
(EM_386 and EM_486), but appears to have been since abandoned.
2a) Are EM_PPC and EM_CYGNUS_POWERPC different processors? 2b) 
If not, why the two definitions?
3) Who decides what are "official" machine types? 
Every document I have found describing the ELF format seems to have a different 
list of "official" values. 
 
If anyone out there can provide any help with these questions, 
I would be very greatful.
 
-Thanks,
David Uczen
Mainframe Systems Programmer

             reply	other threads:[~1999-10-14 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-14 18:38 David and Jannette Uczen [this message]
1999-10-14 19:25 ` Ian Lance Taylor

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='000f01bf16ad$d1148740$9181e3d8@duczen--lap.hannaford.com' \
    --to=uczen@mint.net \
    --cc=binutils@sourceware.cygnus.com \
    /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).