From: "H . J . Lu" <hjl@valinux.com>
To: "David O'Brien" <obrien@FreeBSD.org>
Cc: Alan Modra <alan@linuxcare.com.au>,
Ulrich Drepper <drepper@cygnus.com>,
John Marvin <jsm@udlkern.fc.hp.com>,
parisc-linux@puffin.external.hp.com,
parisc-linux@thepuffingroup.com, binutils@sourceware.cygnus.com
Subject: Re: [parisc-linux] Use of the EI_OSABI field
Date: Sat, 25 Nov 2000 12:33:40 -0800 [thread overview]
Message-ID: <20001125123340.A25382@valinux.com> (raw)
In-Reply-To: <20001125122840.D96258@dragon.nuxi.com>; from obrien@FreeBSD.org on Sat, Nov 25, 2000 at 12:28:40PM -0800
On Sat, Nov 25, 2000 at 12:28:40PM -0800, David O'Brien wrote:
> On Tue, Nov 21, 2000 at 07:11:29PM -0800, H . J . Lu wrote:
> > When I was at the IA64 ABI meeting yesterday, we were looking at the
> > EI_OSABI issue. Everyone at the IA64 ABI meeting agreed that what
> > Ulrich and I had said was the correct understanding.
> >
> > "The e_ident[EI_OSABI] value identifies the operating system and ABI
> > to which the object is targeted" just means if the e_ident[EI_OSABI]
>
>
> Then is this *extremely* misleading text going to be changed???
> "the operating system and" needs to be deleted in the _official_
> _published_ specification.
>
I will bring this issue up to ia64 psABI and gABI.
--
H.J. Lu (hjl@valinux.com)
next prev parent reply other threads:[~2000-11-25 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 5:47 [parisc-linux] Use of the EI_OSABI field John Marvin
2000-11-21 22:50 ` Alan Modra
2000-11-21 23:27 ` Ulrich Drepper
2000-11-22 0:13 ` Alan Modra
2000-11-22 0:31 ` Ulrich Drepper
2000-11-22 0:53 ` H . J . Lu
2000-11-22 3:03 ` Alan Modra
2000-11-22 3:11 ` H . J . Lu
2000-11-25 20:28 ` David O'Brien
2000-11-25 20:33 ` H . J . Lu [this message]
2000-11-22 3:18 ` Ulrich Drepper
2000-11-25 20:31 ` David O'Brien
2000-11-25 20:22 ` David O'Brien
-- strict thread matches above, loose matches on Subject: below --
2000-11-22 8:52 John Marvin
2000-11-22 18:06 Cary Coutant
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=20001125123340.A25382@valinux.com \
--to=hjl@valinux.com \
--cc=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=drepper@cygnus.com \
--cc=jsm@udlkern.fc.hp.com \
--cc=obrien@FreeBSD.org \
--cc=parisc-linux@puffin.external.hp.com \
--cc=parisc-linux@thepuffingroup.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