airborne12 opened a new pull request, #373:
URL: https://github.com/apache/doris-thirdparty/pull/373

   ## Summary
   
   Fix incorrect CPU detection for Intel Emerald Rapids processors (e.g., Intel 
Xeon Platinum 8575C) where they were misidentified as PRESCOTT (Pentium 4 era) 
instead of SAPPHIRERAPIDS.
   
   **Problem:**
   - Intel Xeon Platinum 8575C (model 207 = exmodel 12, model 15) was detected 
as `CORE=PRESCOTT`
   - This caused build failures due to missing FMA/AVX2/AVX512 compiler flags
   - Error: `always_inline function '_mm256_fmadd_ps' requires target feature 
'fma'`
   
   **Root Cause:**
   1. `get_corename()` in `cpuid_x86.c`: case 12 (exmodel 12) only handled 
model 6 (Arrow Lake), missing model 15 (Emerald Rapids)
   2. Missing `break` statement caused fall-through to case 15 (family 15 = 
Pentium 4), returning `CORE_PRESCOTT`
   3. `dynamic.c` lacked runtime detection support for exmodel 10-12 newer 
Intel processors
   
   **Changes:**
   - `cpuid_x86.c`: Add case 15 (Emerald Rapids) to exmodel 12 switch + add 
missing break
   - `driver/others/dynamic.c`: Add runtime detection for:
     - Exmodel 10: Meteor Lake (model 0, 10), Granite Rapids (model 13)
     - Exmodel 11: Raptor Lake, Alder Lake N (model 7, 10, 14, 15)
     - Exmodel 12: Arrow Lake (model 6), Emerald Rapids (model 15)
   
   ## Test plan
   
   - [ ] Verify build succeeds on Intel Xeon Platinum 8575C
   - [ ] Verify CPU is detected as SAPPHIRERAPIDS (or appropriate fallback)
   - [ ] Verify no regression on other Intel processors
   
   🤖 Generated with [Claude Code](https://claude.ai/code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to