public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: x86@gentoo.org, release@gentoo.org
Subject: Re: [gentoo-dev] Gentoo i486 support
Date: Wed, 22 Aug 2018 10:30:33 -0400	[thread overview]
Message-ID: <CAJ0EP40RxR9yUG36a4O9GhbKhPLs9UyBB-AZrrWQ5Pv2P3EbrA@mail.gmail.com> (raw)
In-Reply-To: <5cc35530-3d96-1a0f-b484-73ea3d58bed5@gentoo.org>

On Wed, Aug 22, 2018 at 8:26 AM Ben Kohler <bkohler@gentoo.org> wrote:
>
> Hi guys,
>
> For some time now, we've been shipping broken i486 stage3s that do not
> run on pre-i686 hardware [1].  Due to a change in catalyst [2], we no
> longer set CXXFLAGS in the default make.conf, so the x86 profiles' (imho
> wrong/broken) defaults [3] kick in.
>
> I'd like to get this fixed, and I see 3 possible solutions, listed in
> order of my own preference:
>
> 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.

Based on a quick test, running i686-pc-linuc-gnu-gcc without passing
-march seems to be equivalent to passing "-mtune=generic -march=i686".
So, you'll get code that will only run on i686, but has "generic"
tuning (whatever that means).

I don't think that will make a noticeable difference on user systems.
Most Gentoo people probably override this to some more specific CPU
model via CFLAGS in make.conf anyway.

So +1 from me on removing -march=i686 from the x86 arch profile.


  parent reply	other threads:[~2018-08-22 14:30 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
2018-08-22 13:21 ` James Le Cuirot
2018-08-22 14:30 ` Mike Gilbert [this message]
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=CAJ0EP40RxR9yUG36a4O9GhbKhPLs9UyBB-AZrrWQ5Pv2P3EbrA@mail.gmail.com \
    --to=floppym@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