public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Kohler <bkohler@gentoo.org>
To: gentoo-dev@lists.gentoo.org, x86@gentoo.org, release@gentoo.org
Subject: [gentoo-dev] Gentoo i486 support
Date: Wed, 22 Aug 2018 07:26:24 -0500	[thread overview]
Message-ID: <5cc35530-3d96-1a0f-b484-73ea3d58bed5@gentoo.org> (raw)

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.

2) Patch catalyst to start setting CXXFLAGS again.  Rather than roll 
back to exactly CXXFLAGS="${CFLAGS}" again, it's been suggested that we 
start setting COMMON_FLAGS, and CFLAGS="${COMMON_FLAGS}" 
CXXFLAGS=${COMMON_FLAGS}" etc.  I prepared such a patch a while back 
[4], which seems to work but may need a bit of updating.

3) Drop i486 support.  We're only pretending to have support now, we 
could officially stop building these broken stages completely.

Personally I think #1 is the most technically correct and least amount 
of work.  The only result will be slightly less optimized builds for 
people who choose not to customize *FLAGS at all in make.conf.  But this 
is correct behavior.  What we have now is akin to setting -march=core2 
on amd64 stage3 and saying "oops it doesn't work on early 64bit AMD 
cpus, but oh well most people have newer and will appreciate the 
optimization".

Thoughts?

-Ben

[1] https://bugs.gentoo.org/654080
[2] 
https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=b409bd9bb4b50f69a555e4e148057ade86a7ed16
[3] 
https://gitweb.gentoo.org/repo/gentoo.git/tree/profiles/arch/x86/make.defaults
[4] https://bugs.gentoo.org/575446#c4


             reply	other threads:[~2018-08-22 12:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 12:26 Ben Kohler [this message]
2018-08-22 13:08 ` [gentoo-dev] Gentoo i486 support 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
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=5cc35530-3d96-1a0f-b484-73ea3d58bed5@gentoo.org \
    --to=bkohler@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