Bug#930935: webkit2gtk: Baseline violation on i386
bunk at debian.org
Sun Jun 23 22:34:26 BST 2019
Control: tags -1 -patch
Looking again at the code it seems my patch is actually wrong,
and wonder whether WTF_CPU_UNKNOWN might be the correct approach.
On Sun, Jun 23, 2019 at 10:23:41PM +0200, Alberto Garcia wrote:
> Building with SSE2 is not a decision made by the Debian maintainers.
> Upstream WebKit dropped support for non-SSE2 processors and the code
> assumes that SSE2 is always available:
"as part of Igalia's work on 32bit support"
"there were no negative comments"
Someone should have told upstream at Igalia that non-SSE is supported
by the Debian i386 port.
> As far as I'm aware this is also happening with other browsers,
> e.g. Chromium dropped support 5 years ago:
IMHO this should be a reason for dropping i386 from the chromium
> And so did Firefox:
The Debian maintainers have patched both Rust and Firefox to make them
work on non-SSE i386 despite upstream no longer supporting it.
There were plenty of bug reports when an SSE-using Firefox recently
slipped through - and in general based on the numbers of bugs submitted
non-SSE i386 has more users than half our release architectures combined.
And Firefox is only a browser, the prospect that various parts of the
default desktop might be crashing on supported hardware is not nice.
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
More information about the Pkg-webkit-maintainers