From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Tom Vier <tmv5@home.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, rth@twiddle.net
Subject: Re: [patch] Re: Linux 2.4.5-ac6
Date: Wed, 06 Jun 2001 10:49:14 -0400 [thread overview]
Message-ID: <3B1E42EA.B0AE7F6E@mandrakesoft.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1010606115046.23232A-100000@delta.ds2.pg.gda.pl>
"Maciej W. Rozycki" wrote:
>
> On Wed, 6 Jun 2001, Ivan Kokshaysky wrote:
>
> > > No need to patch arch_get_unmapped_area(), but OSF/1 compatibility code
> > > might need fixing. I suppose an OSF/1 binary must have an appropriate
> > > flag set in its header after building with the -taso option so that the
> > > system knows the binary wants 32-bit addressing.
> >
> > I'm not sure if COFF headers have such flag at all. I'll check this.
>
> Then how does OSF/1, especially the dynamic linker, know if a binary
> needs 32-bit addressing? I suppose we could use the same way of
> selection.
There are two things you can do here, one is easy: use linker tricks to
make sure that an application built on alpha -- with 64-bit pointers --
uses no more than the lower 32 bits of each pointer for addressing.
This should fix a ton of applications which cast pointer values to ints
and similar garbage.
The other option, hacking gcc to output "32-bit alpha" binary code, is a
tougher job.
I had mentioned this to Richard Henderson a while back, when I was
wondering how easy it is to implement -taso under Linux, and IIRC he
seemed to think that linker tricks were much easier.
Jeff
--
Jeff Garzik | An expert is one who knows more and more about
Building 1024 | less and less until he knows absolutely everything
MandrakeSoft | about nothing.
next prev parent reply other threads:[~2001-06-06 14:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 11:01 Linux 2.4.5-ac6 Alan Cox
2001-06-01 11:28 ` Alexander Viro
2001-06-01 11:52 ` Alan Cox
2001-06-01 12:23 ` Keith Owens
2001-06-02 2:27 ` Tom Vier
2001-06-04 10:16 ` Maciej W. Rozycki
2001-06-04 17:08 ` [patch] " Ivan Kokshaysky
2001-06-05 15:11 ` Maciej W. Rozycki
2001-06-05 17:41 ` Ivan Kokshaysky
2001-06-05 18:32 ` Maciej W. Rozycki
2001-06-06 5:37 ` Ivan Kokshaysky
2001-06-06 13:09 ` Maciej W. Rozycki
2001-06-06 14:49 ` Jeff Garzik [this message]
2001-06-06 17:26 ` Maciej W. Rozycki
2001-06-07 17:48 ` Ivan Kokshaysky
2001-06-07 18:31 ` Maciej W. Rozycki
2001-06-08 10:18 ` jlnance
2001-06-08 17:06 ` Gerhard Mack
2001-06-08 14:18 ` Ivan Kokshaysky
2001-06-07 17:20 ` Ivan Kokshaysky
2001-06-07 18:28 ` Maciej W. Rozycki
2001-06-08 14:16 ` Ivan Kokshaysky
2001-06-08 16:08 ` Maciej W. Rozycki
2001-06-08 17:23 ` Ivan Kokshaysky
2001-06-09 10:14 ` Ivan Kokshaysky
2001-06-09 18:46 ` Tom Vier
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=3B1E42EA.B0AE7F6E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=rth@twiddle.net \
--cc=tmv5@home.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