Stop testing builds with runtime-detected NEON
O frabjous day! Chrome has switched on requiring NEON globally at head. Android has always built with NEON as appropriate for each device. In practice, this switches our Nexus 5 bots from runtime-detected to building with NEON globally. It also lines a few columns up and makes equivalent aliases more obviously the same. We still have Build bots to test we can build on ARMv7 with no NEON. (We even have Build bots to test building ARMv6.) (It looks like that buildbot_spec.json just hasn't been updated in a while.) BUG=skia: GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1612753002 CQ_EXTRA_TRYBOTS=client.skia.android:Perf-Android-GCC-Nexus5-CPU-NEON-Arm7-Release-Trybot,Test-Android-GCC-Nexus5-CPU-NEON-Arm7-Debug-Trybot,Test-Android-GCC-Nexus5-CPU-NEON-Arm7-Release-Trybot Review URL: https://codereview.chromium.org/1612753002
This commit is contained in:
parent
f6c7107d03
commit
80fc19cd3a
File diff suppressed because it is too large
Load Diff
@ -215,16 +215,16 @@ def device_cfg(builder_dict):
|
||||
}.get(builder_dict['target_arch'], 'arm_v7_neon')
|
||||
elif builder_dict.get('os') == 'Android':
|
||||
return {
|
||||
'AndroidOne': 'arm_v7_neon',
|
||||
'GalaxyS3': 'arm_v7_neon',
|
||||
'GalaxyS4': 'arm_v7_neon',
|
||||
'Nexus5': 'arm_v7', # This'd be 'nexus_5', but we simulate no-NEON Clank.
|
||||
'Nexus6': 'arm_v7_neon',
|
||||
'Nexus7': 'nexus_7',
|
||||
'Nexus9': 'nexus_9',
|
||||
'Nexus10': 'nexus_10',
|
||||
'NexusPlayer': 'x86',
|
||||
'AndroidOne': 'arm_v7_neon',
|
||||
'GalaxyS3': 'arm_v7_neon',
|
||||
'GalaxyS4': 'arm_v7_neon',
|
||||
'NVIDIA_Shield': 'arm64',
|
||||
'Nexus10': 'arm_v7_neon',
|
||||
'Nexus5': 'arm_v7_neon',
|
||||
'Nexus6': 'arm_v7_neon',
|
||||
'Nexus7': 'arm_v7_neon',
|
||||
'Nexus9': 'arm64',
|
||||
'NexusPlayer': 'x86',
|
||||
}[builder_dict['model']]
|
||||
|
||||
# ChromeOS.
|
||||
|
Loading…
Reference in New Issue
Block a user