chromium-browser crashes with SIGILL if CPU does not support SSE2

[A. Eibach]

My CPU does not support SSE2, this is a fact.

And as far as I knew (unless I missed something) for the use of Chromium on Linux, there was nowhere a *requirement* listed that a SSE2-capable CPU would be mandatory.
For instance, old(er) Athlon XP machines support SSE, but not SSE2.

I've run a DEBUG build of chromium v41 to demonstrate this fact.

These are the most evident 2 lines:

#
# Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82
# CHECK(cpu.has_sse2()) failed
#

Looks to me that the more recent _asm routines now _blindly_ assume that the CPU is capable of SSE2 instruction set.
If you really CAN'T help the cool feeling of locking us out (I think we still are millions of users worldwide with Athlon XP machines), we can't stop you.
But at least the browser should exit more gracefully if this is the case, but not crash with a SIGILL.

[Chad Miller (cmiller)]

Please open a Terminal and run.

$ apport-collect 1437070

[Chad Miller (cmiller)]

Also,

$ grep ^flags.\*:.\*\\bcmov\\b /proc/cpuinfo

[Olivier Tilloy (osomon)]

This was marked fixed upstream.