mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: joebob@spamtest.viacore.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pure 64 bootloaders
Date: Mon, 12 Sep 2005 15:12:30 -0700 (PDT)	[thread overview]
Message-ID: <20050912.151230.100651236.davem@davemloft.net> (raw)
In-Reply-To: <4325FADB.4090804@spamtest.viacore.net>

From: Joe Bob Spamtest <joebob@spamtest.viacore.net>
Date: Mon, 12 Sep 2005 15:02:03 -0700

> David S. Miller wrote:
> >>agreed -- as far as i'm concerned the 32 bit libraries are there for 
> >>compatibility's sake and should be in /lib/compat/<subarch> instead of 
> >>/lib. the native libraries should be in /lib instead of /lib64. lib64 
> >>should just go away!
> > 
> > 64-bit isn't any more "native" than 32-bit on some 64-bit platforms.
> > 32-bit is the default and most desirable userland binary format on
> > sparc64 for example.  So 32-bit programs on sparc64 are as "native" as
> > 64-bit ones might be considered.
> 
> that's true, i had forgotten about the sparc64 case. it really does slow 
> down tremendously when used in pure 64 bit mode

PPC64 is the same, as well as a few others are likely to
be in this boat as well.  The only known exception where
64-bit is a true win is x86_64.

> i would imagine this not to be the case for most architectures though. 
> possibly hppa is the same way. anyone with mips64 and ppc64 hardware out 
> there have any input?

See above.

  reply	other threads:[~2005-09-12 22:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10  7:42 Jim Gifford
2005-09-10  7:52 ` Jeff Garzik
2005-09-10  8:01 ` David S. Miller
2005-09-11 16:33   ` Jim Gifford
2005-09-11 18:48     ` David S. Miller
2005-09-11 18:49     ` David S. Miller
2005-09-10  8:28 ` Andi Kleen
2005-09-10  8:39   ` Jeff Garzik
2005-09-10 16:34     ` Chris Wedgwood
2005-09-10 18:15       ` David S. Miller
2005-09-12 21:32       ` Joe Bob Spamtest
2005-09-12 21:41         ` David S. Miller
2005-09-12 22:02           ` Joe Bob Spamtest
2005-09-12 22:12             ` David S. Miller [this message]
2005-09-12 23:09               ` Joe Bob Spamtest
2005-09-13 16:52                 ` Lennart Sorensen
2005-09-13 17:00                   ` Joe Bob Spamtest
2005-09-14  3:44                     ` Kyle Moffett
2005-09-14 13:20                       ` Lennart Sorensen
2005-09-14 17:26                         ` Kyle Moffett
2005-09-13 17:21                   ` Maciej W. Rozycki
2005-09-13 19:37                     ` Lennart Sorensen
2005-09-14  9:39                       ` Maciej W. Rozycki
2005-09-10 18:30     ` Harald Dunkel
2005-09-12 14:50       ` Roger Heflin
2005-09-13 17:14         ` Bastian Blank
2005-09-15  6:16         ` Harald Dunkel
2005-09-11 11:53   ` Stephen Frost
2005-09-11 14:14     ` Stefan Smietanowski

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=20050912.151230.100651236.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=joebob@spamtest.viacore.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®