From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Arthur Zamarin <arthurzam@gentoo.org>
Subject: Re: x86 FP issues (Re: [gentoo-dev] Arch Status and Future Plans)
Date: Fri, 28 Jun 2024 07:20:12 +0200 [thread overview]
Message-ID: <baa1ca92da4941b0999ea2feecf02334b5b20ade.camel@gentoo.org> (raw)
In-Reply-To: <87tthgo8pt.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]
On Wed, 2024-06-26 at 01:20 +0100, Sam James wrote:
> Arthur Zamarin <arthurzam@gentoo.org> writes:
>
> > Hi all, this will be a long mail, and might be confusing, I'll try to
> > organize it, but this is a mess, so bear with me.
> > [...]
> > ======== 32-bit arches ========
> >
> > This includes stable arches x86, arm, ppc, sparc32, dev arches s390, and
> > maybe more. Those are in much worse situation, with a mess on various
> > fronts, some of them super hard to continue support. For example
> > qtwebengine is less and less likely to manage to compile on a
> > real-hardware, and not 32-bit chroot on 64-bit host. Arch Team want to
> > minimize our work on those arches, meaning mass-destable and even
> > mass-dekeyword, with potentially full drop of stable status.
> >
> > ======== x86 ========
> >
> > Stable 32-bit arch. I'll be honest, I don't believe at all this should
> > be stable arch anymore. I propose making it dev arch, and mass-dekeyword
> > stuff we got because of inertia. This arch is close to HW die. (let's
> > not talk about i486 vs i686).
>
> I think the mfpmath=sse thing [0] makes this a bit better but I still
> sympathise with your point.
I'd just like to point out that `-mfpmath=sse` is a two-edged sword. It
generally makes results more consistent with other architectures which
is good and resolves some test failures when people *aren't testing with
x86*. However, it breaks stuff when people are specifically testing
with x86 and accounting for i387 math (sigh).
>
> [0] https://public-inbox.gentoo.org/gentoo-dev/ce894afe6c2b324fef012da9bb9387cfde7aed03.camel@gentoo.org/
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2024-06-28 5:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 17:33 [gentoo-dev] Arch Status and Future Plans Arthur Zamarin
2024-06-25 21:40 ` matoro
2024-06-25 22:55 ` James Le Cuirot
2024-06-26 0:06 ` Notion of stable depgraph vs stable keywords (Re: [gentoo-dev] Arch Status and Future Plans) Sam James
2024-06-28 4:17 ` [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: " Duncan
2024-06-28 5:16 ` Sam James
2024-06-26 0:14 ` Misc arch plans (Re: [gentoo-dev] " Sam James
2024-06-26 20:29 ` ia64, was: " Andreas K. Huettel
2024-06-26 20:45 ` matoro
2024-06-26 0:17 ` On the value (or not?) of stable keywords " Sam James
2024-06-26 0:19 ` time64 & LFS for 32-bit arches " Sam James
2024-06-26 0:20 ` x86 FP issues " Sam James
2024-06-28 5:20 ` Michał Górny [this message]
2024-06-26 7:38 ` [gentoo-dev] Re: Arch Status and Future Plans Florian Schmaus
2024-06-26 8:29 ` Christian Bricart
2024-06-26 20:44 ` Immolo
2024-06-26 19:47 ` nomenclature, was: Re: [gentoo-dev] " Andreas K. Huettel
2024-06-26 20:18 ` Andreas K. Huettel
2024-06-26 20:24 ` riscv, was: " Andreas K. Huettel
2024-06-26 21:08 ` 32bit vs 64bit, " Andreas K. Huettel
2024-06-28 16:12 ` splitting keywords, " Andreas K. Huettel
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=baa1ca92da4941b0999ea2feecf02334b5b20ade.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=arthurzam@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