From b13016e55a37757d39c458784ffe5e6be91da1e7 Mon Sep 17 00:00:00 2001 From: Abseil Team Date: Tue, 29 Aug 2023 11:58:03 -0700 Subject: 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 --- absl/crc/internal/crc_memcpy_x86_64.cc | 1 - 1 file changed, 1 deletion(-) 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: -- cgit v1.2.3