From: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Stephen P. Becker" <geoman@gentoo.org>,
Frederic TEMPORELLI - astek <ftemporelli@astek.fr>,
linux-mips@linux-mips.org
Subject: Re: IP32 - issues with last CVS snapshoot
Date: Fri, 11 Feb 2005 11:34:25 -0800 [thread overview]
Message-ID: <420D08C1.8050105@total-knowledge.com> (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 know
> 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...
>
>
Because they hope that if they annoy you enough, you'll do it yourself ;-)
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com
next prev parent reply other threads:[~2005-02-11 19:34 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 [this message]
2005-02-11 19:50 ` Maciej W. Rozycki
2005-02-11 19:38 ` Stephen P. Becker
2005-02-12 0:53 ` Kumba
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=420D08C1.8050105@total-knowledge.com \
--to=ilya@total-knowledge.com \
--cc=ftemporelli@astek.fr \
--cc=geoman@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@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