From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo i486 support
Date: Sat, 25 Aug 2018 14:07:39 +0300 [thread overview]
Message-ID: <20180825140739.1f2eadb1a545562ba72b4cec@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=5T+TihqVhGT-s+WPEmi+jSn4qgYwFatq7fGi7CZ4D5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2747 bytes --]
Hi!
On Wed, 22 Aug 2018 09:08:06 -0400 Rich Freeman wrote:
> On Wed, Aug 22, 2018 at 8:26 AM Ben Kohler <bkohler@gentoo.org> wrote:
> >
> > 1) Adjust x86 profile defaults to drop the problematic -march=i686.
> > This would be more in line with amd64 profiles (et al), which set no
> > -march value so it can run on any hardware for this arch.
> >
>
> My knee-jerk reaction was that this is a bad idea, but after a bit of
> thought there are some arguments in favor of this:
>
> First, the argument against: i386 is VERY old. Most distros moved
> their defaults to i686 because it had significant improvements, and
> i686 was still mainstream but i386 was ancient. In contrast with
> amd64 the entire architecture is fairly new and the baseline doesn't
> suffer from many of the issues i386 suffers compared to i686. This is
> a really short synopsis - if you go to any distro list archive you can
> find long passionate arguments from ~10 years ago that elaborated on
> this. In that sense, going back to i386 is turning back the clock.
>
> HOWEVER, I think there is an argument for i386 that wasn't so valid
> back then. x86 in general is starting to look a bit like i386. What
> are the main use cases for it in this day and age? I don't use x86,
> so I'm not the best person to answer that. However, I'd broadly split
> it into two categories (mostly by tautology):
>
> 1. Museum hardware. People have systems that are running simply
> BECAUSE they are old, not because they are cost-effective/etc. I'm
> not sure I'd even lump used hardware into this category any longer, as
> I'm sure there are plenty of i686+ used PCs at rock-bottom prices
> already out there, and maintaining pre-Y2K hardware is going to be
> fairly painful. For this use case i386 as the baseline makes a LOT of
> sense.
>
> 2. Non-museum hardware. People have x86 hardware because it is the
> most cost-effective solution for a task, and not merely because it is
> old. IMO for this use case i686 makes a lot more sense as a baseline.
> However, I'm honestly not sure in this day and age what these use
> cases even are, unless it is something you can buy for $10 at a flea
> market. Even if you're talking about a container running one
> application that only needs 500kB of RAM, is there really that much
> benefit to not building it for amd64?
As active x86 hardware user I can add:
3. Security. CPUs without speculative execution and L3 cache are
much more secure by design. Thanks to the virtues of Gentoo
(highest possible code optimization and ability to USE light
versions of applications) such hardware (e.g. 32bit Atoms) is still
usable quite fine.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-25 11:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 12:26 [gentoo-dev] Gentoo i486 support Ben Kohler
2018-08-22 13:08 ` Rich Freeman
2018-08-22 13:23 ` Mart Raudsepp
2018-08-22 14:22 ` Peter Stuge
2018-08-22 20:27 ` R0b0t1
2018-08-22 20:39 ` Rich Freeman
2018-08-25 11:07 ` Andrew Savchenko [this message]
2018-08-22 13:21 ` James Le Cuirot
2018-08-22 14:30 ` Mike Gilbert
2018-08-22 15:27 ` Thomas Deutschmann
2018-08-22 19:20 ` Matt Turner
2018-08-22 19:27 ` M. J. Everitt
2018-08-22 20:19 ` Richard Yao
2018-08-24 13:19 ` Kent Fredric
2018-08-24 13:57 ` Mike Gilbert
2018-08-24 14:13 ` Rich Freeman
2018-08-24 14:40 ` Kent Fredric
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=20180825140739.1f2eadb1a545562ba72b4cec@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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