From: jhe2 <jhe2@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] add sse flags to i686 profile
Date: Mon, 22 Jul 2024 14:21:39 +0200 [thread overview]
Message-ID: <20240722122139.960C923AB2@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51333@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
New comment by jhe2 on void-packages repository
https://github.com/void-linux/void-packages/pull/51333#issuecomment-2242824863
Comment:
> > most of the failures to boot i686 live images i see are OOMs
>
> How many people are actually booting Void on pre-2001 hardware?
I can't tell you that, but AMD has built CPUs based on the Athlon XP (which is a 32-bit CPU with SSE1, but without SSE2) until 2006. The latest of those CPUs were sold under their budget Sempron brand.
Sometimes I run Void on vintage hardware (e.g. on Pentium III machines), not out of necessity, but more because it is fun and can be helpful to get data onto/off of the machine.
If you don't want to support such old machines, that is understandable, if a little bit unfortunate. When going that route though, I would probably drop i686 all together.
next prev parent reply other threads:[~2024-07-22 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 19:35 [PR PATCH] " Calandracas606
2024-07-18 19:39 ` [PR REVIEW] " Calandracas606
2024-07-18 19:39 ` Calandracas606
2024-07-20 4:31 ` classabbyamp
2024-07-20 23:01 ` tornaria
2024-07-21 1:46 ` sgn
2024-07-21 1:54 ` classabbyamp
2024-07-22 9:28 ` jhe2
2024-07-22 11:01 ` leahneukirchen
2024-07-22 12:21 ` jhe2 [this message]
2024-07-22 12:41 ` leahneukirchen
2024-07-22 13:11 ` jhe2
2024-10-21 2:01 ` github-actions
2024-10-21 12:37 ` Calandracas606
2025-01-21 1:57 ` github-actions
2025-02-04 1:57 ` [PR PATCH] [Closed]: " github-actions
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=20240722122139.960C923AB2@inbox.vuxu.org \
--to=jhe2@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).