The fix is relatively simple, but I honestly have no idea at all where to start with to figure out what "Chrome PFQ on ARM" even means. Maybe I'll just entirely disable the intrinsic in question for clang.
SO, to be clear, we need to either quickly fix this or re-revert it (and kindly not unrevert without fixing the described bug).
This is blocking Chrome OS releases and developers.
Confirmed the compilation failure on Chrome OS/ARM has been fixed and Chrome has been uprev'ed :-)
shess@, I'll leave it up to you to close the bug, in case there's still more work to be done on that feature. But at least as far as issue in #7 is concerned, that's fixed. Thank you!
I'm going to let it idle for a couple weeks before removing the old version and closing. Usually/often there will be one or two subtle bugs which we can't see until they reach dev or beta.
Comment 1 by sh...@chromium.org
, Mar 14 2017