![]() ![]() Completely spitballing maybe it's less a GCC issue than makefile problems Debian might be sticking with the old-fashioned "i686 means Pentium Pro" definition while Ubuntu is trying to do it Arch's way (which should make Pentium III the floor, a Pentium II would be screwed by the SSE requirement) but developers are inconsistent about compiler flags in a way that accidentally made Pentium4/PentiumM the basement. but it is also apparently a known bug that SSE2-needful-packages keep slipping into their i686 build.Ĭonsidering Ubuntu's inclinations to be less conservative than upstream Debian it could well be they had the same issues as Arch. Here is the Pale Moon forum thread: PaleMoon 27.0.1 doesn't display correctly on - Pale Moon forum. It should be fixed in Pale Moon 27.1.0 ( i don't think that will be the next release). Sorry Guys if I moved these stuff from the Windows 10 thread, but I think that these handy instructions are worth a whole topic for them. DavidE said: I posted about this on the Pale Moon forum. ![]() The Windows 10 mega-thread Unread post by darkmoon » Thu 9:12 pm Tomaso wrote. Arch Linux, for instance, says i686 doesn't just mean CMOV, it also needs to support MMX and SSE, but not SSE2. Discussion forum for the Pale Moon web browser. (IE, it *should* still run on a Pentium Pro, with CMOV and PAE the major breaking points for the K6 and some VIA chips that otherwise are more featureful) But digging around it looks like the exact meaning of "i686" has been blurring. FWIW, Debian's documentation says that they still compile their 32 bit distribution to target "686", which if it means what it used to mean "back in the day" it shouldn't rely on SSE, or even MMX, instructions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |