[Webkit-unassigned] [Bug 197192] [GTK][WPE][JSCOnly] compile error when -DWTF_CPU_ARM64_CORTEXA53=ON set for arm64

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=197192

--- Comment #3 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
Our current Linux JSCOnly ARM64 test bot happens to be an x86_64 machine that cross-builds and then runs the tests remotely.

Because it cross-builds its not enabling the workaround by default

The test machine where it currently runs is a Raspberry Pi 3, which happens to be an ARM Cortex A53 with a revision 4 of the core (r0p4)

        # head /proc/cpuinfo
        processor       : 0
        BogoMIPS        : 38.40
        Features        : fp asimd evtstrm crc32
        CPU implementer : 0x41
        CPU architecture: 8
        CPU variant     : 0x0
        CPU part        : 0xd03
        CPU revision    : 4

        [....]


So, in theory, it would be affected by this erratum 835769. In practice I'm not 100% sure if its affected. But its the closed hardware I have that might have the bug.


And according to the current test results https://build.webkit.org/builders/JSCOnly%20Linux%20AArch64%20Release things seems to be fine there, right?
So I guess that either the workaround is not necessary anymore, or that the RPi3 is not affected.

But, even if we assume that the RPi3 is not affected, the workaround its not building anymore, and we can't test it works because we don't have hardware.

And previously it was not getting enabled by default (only when the build machine was a Cortex A53 ... and native building on ARM is not the usual way of building WebKit).


So I think we should just remove this code for the workaround unless there is some bug report about this issue or a way to test it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191008/9bc64da7/attachment-0001.html>