From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: IP32 - issues with last CVS snapshoot
Date: Fri, 11 Feb 2005 19:53:08 -0500 [thread overview]
Message-ID: <420D5374.4000006@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0502111915510.30117@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
> On Fri, 11 Feb 2005, Ilya A. Volynets-Evenbakh wrote:
>
>
>>O64 may not be supported ABI, but it provides us with a feature that is really
>>usefull:
>>specifically, it generates 32 bit symbol addresses instead of 64 bit ones.
>>This cuts
>>down on code size considerably. If this feature was implemented in toolchain
>>as separate
>>switch, O64 hack could go away.
>
>
> Well, the topic has been beaten to death here, so you don't really need
> to illuminate me -- it's only due to this popular request I've implemented
> the ability to do 32-bit builds for 64-bit kernel. I just wonder why
> people insisting on such a setup don't actually contribute some code to do
> that cleanly and keep switching between hacks as they stop working one by
> one...
>
I believe it was mentioned at some point in time by someone that using "n32"
inplace of "o64" might have a similar affect of "o64", but I can't recall what
the outcome of that actually was (or whether or not it ever worked).
As if I could be any more vague.
--Kumba
--
--
"Such is oft the course of deeds that move the wheels of the world: small
hands do them because they must, while the eyes of the great are elsewhere."
--Elrond
next prev parent reply other threads:[~2005-02-12 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 17:42 IP32 - issues with last CVS snapshoot Frederic TEMPORELLI - astek
2005-02-11 18:14 ` Stephen P. Becker
2005-02-11 18:41 ` Maciej W. Rozycki
2005-02-11 18:58 ` Ilya A. Volynets-Evenbakh
2005-02-11 19:27 ` Maciej W. Rozycki
2005-02-11 19:34 ` Ilya A. Volynets-Evenbakh
2005-02-11 19:50 ` Maciej W. Rozycki
2005-02-11 19:38 ` Stephen P. Becker
2005-02-12 0:53 ` Kumba [this message]
2005-02-12 1:54 ` Ralf Baechle
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=420D5374.4000006@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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