From: "David and Jannette Uczen" <uczen@mint.net>
To: <linas@linas.org>
Cc: <ian@zembu.com>, <binutils@sourceware.cygnus.com>, <linas@linas.org>
Subject: Re: IBM S/370 and binutils
Date: Fri, 29 Oct 1999 18:27:00 -0000 [thread overview]
Message-ID: <003401bf2275$bc5d1c80$4181e3d8@duczen--lap.hannaford.com> (raw)
You should be able to get an ABI from Amdahl Corporation, through UTS
Technical Support. I have contacted a Chris A. Swartout
(cas30@oes.amdahl.com), who verified that the value of EM_S370 (9) is used
for IBM System/370 Processors. This value still exists in the binutils
source (/binutils/include/elf/common.h).
I have had the value officially registered with SCO (registry@sco.com). A
new ABI is going to be published soon.
I myself am trying to get ABI information, but haven't heard back yet.
--David
-----Original Message-----
From: linas@linas.org <linas@linas.org>
To: David and Jannette Uczen <uczen@mint.net>
Cc: ian@zembu.com <ian@zembu.com>; binutils@sourceware.cygnus.com
<binutils@sourceware.cygnus.com>; linas@linas.org <linas@linas.org>
Date: Friday, October 29, 1999 12:22 PM
Subject: Re: IBM S/370 and binutils
>> -----Original Message-----
>> From: Ian Lance Taylor <ian@zembu.com>
>> To: uczen@mint.net <uczen@mint.net>
>> Cc: binutils@sourceware.cygnus.com <binutils@sourceware.cygnus.com>
>> Date: Wednesday, October 27, 1999 7:40 PM
>> Subject: Re: IBM S/370 and binutils
>>
>>
>> > From: "David and Jannette Uczen" <uczen@mint.net>
>> > Date: Wed, 27 Oct 1999 19:22:49 -0400
>> >
>> > I am forwarding this message to inform the binutils developers that I
>> > believe that any further use of the ELF machine type EM_I370 (0xF00F)
>> should
>> > be discontinued.
>
>Ian,
>
>I picked this value in the absence of any other suitable value.
>There is no formal ELF ABI that would specify such a value,
>although I have been working on & off with folks inside of IBM
>(the TJ Watson research center) to create such an ABI. Clearly,
>among the first steps would be to designate a machine type.
>
>Please let me know who I should contact to get this (and also,
>a type for the binary format) reserved in the most suitably
>official manner possible.
>
>--linas
>
>
next reply other threads:[~1999-10-29 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 18:27 David and Jannette Uczen [this message]
1999-10-30 11:45 ` linas
-- strict thread matches above, loose matches on Subject: below --
1999-10-30 19:32 David and Jannette Uczen
1999-10-30 10:01 David and Jannette Uczen
1999-10-30 10:57 ` linas
1999-10-29 18:37 David and Jannette Uczen
1999-10-29 18:27 David and Jannette Uczen
1999-10-27 18:40 David and Jannette Uczen
1999-10-27 19:19 ` Alan Modra
1999-10-29 9:12 ` linas
1999-10-29 9:28 ` H.J. Lu
1999-10-29 9:37 ` Ian Lance Taylor
1999-10-29 10:53 ` linas
1999-10-29 9:14 ` linas
1999-10-29 9:22 ` linas
1999-10-29 9:36 ` Ian Lance Taylor
1999-10-29 9:57 ` H.J. Lu
1999-10-29 10:05 ` H.J. Lu
1999-10-27 16:24 David and Jannette Uczen
1999-10-27 16:40 ` 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='003401bf2275$bc5d1c80$4181e3d8@duczen--lap.hannaford.com' \
--to=uczen@mint.net \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.com \
--cc=linas@linas.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).