On 2014/06/20 11:40:07, ulan wrote:
[+Ross for Android perspective]
I wonder about cost vs benefit of this change. At the moment we do not
test or
run benchmarks for Aarch32. After this change we will have to. I am not
sure
of
there are embedders that going to run 32-bit V8 on arm64. Do you have any
in
mind?
From the point of view of Chrome on Android, we don't have any plans to
target
aarch32 currently. The plan is that we run targeting aarch64 on arm-v8
chips,
so I don't think there would be any situations where we would run on an
arm-v8
chip and not be using the arm64 backend (this may change in the future of
course). The Android WebView will run both on 32bit and 64 bit processes,
so we
could conceivably target aarch32 instructions there if we probed and found
we
were running on an arm-v8 chip. I'm not sure if this would be worth it
though -
Do these instructions make significant performance improvements over armv7?
https://codereview.chromium.org/322423003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
