From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Gentoo x86 AT <x86@gentoo.org>, release@gentoo.org
Subject: Re: [gentoo-dev] Gentoo i486 support
Date: Wed, 22 Aug 2018 16:23:02 +0300 [thread overview]
Message-ID: <1534944182.4158.6.camel@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=5T+TihqVhGT-s+WPEmi+jSn4qgYwFatq7fGi7CZ4D5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
Ühel kenal päeval, K, 22.08.2018 kell 09:08, kirjutas Rich Freeman:
> 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.
The topic is i486, not i386.
i486 stages allows to more easily start up gentoo on i486 and i586
hardware, possibly also for some i686.
E.g. if I'd ever get around to working on Geode graphics again, I would
want a i486 or i586 stage to start with, as CMOV on the Geode is a
performance penalty, not benefit, plus glibc i486 or i586 glibc
intrinsics were faster than i686 ones as well. This includes a million
or so OLPC XO-1's out there, not that they'd ever install Gentoo
though, but just an example. I think some old VIAs are another?
i686 builds sometimes wrongly make use of NOPL instruction as well,
though hopefully that was fixed for good in binutils.
Anyways, my point is that we are talking about being able to boot i486
and i586 here, not i386.
Personally I can manage my potential own future needs without weekly
stages.
Mart
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-08-22 13:23 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 [this message]
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
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=1534944182.4158.6.camel@gentoo.org \
--to=leio@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=release@gentoo.org \
--cc=x86@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