diff options
author | Abseil Team <absl-team@google.com> | 2023-08-29 11:58:03 -0700 |
---|---|---|
committer | Copybara-Service <copybara-worker@google.com> | 2023-08-29 11:58:50 -0700 |
commit | b13016e55a37757d39c458784ffe5e6be91da1e7 (patch) | |
tree | 8fa48e66a36159ee61b85686f499c1dc23945681 /absl | |
parent | ded2ec077d911de647d47ab48ef3a8e24a1fb64a (diff) |
Use fallback engine for as the non-temporal engine for unknown CPU types
Using the non-temporal AVX engine for unknown CPU types looks like a mistake to
me, and the default built into the switch case is to use the fallback engine. I
don't think this is causing issues now, but it might once we add ARM support.
PiperOrigin-RevId: 561097994
Change-Id: I7f0edd447017c09acd49e4ea11476e32740d630a
Diffstat (limited to 'absl')
-rw-r--r-- | absl/crc/internal/crc_memcpy_x86_64.cc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/absl/crc/internal/crc_memcpy_x86_64.cc b/absl/crc/internal/crc_memcpy_x86_64.cc index c39b061c..35d1273e 100644 --- a/absl/crc/internal/crc_memcpy_x86_64.cc +++ b/absl/crc/internal/crc_memcpy_x86_64.cc @@ -348,7 +348,6 @@ CrcMemcpy::ArchSpecificEngines CrcMemcpy::GetArchSpecificEngines() { // Get the underlying architecture. CpuType cpu_type = GetCpuType(); switch (cpu_type) { - case CpuType::kUnknown: case CpuType::kAmdRome: case CpuType::kAmdNaples: case CpuType::kIntelCascadelakeXeon: |