fix(data): resolve 8 more ambiguous Intel CPU slugs - #336
Merged
Merged
Conversation
github-actions
Bot
added
bug
Source-verify against Intel ARK, Wikipedia processor lists and TechPowerUp the residual ambiguities left unresolved by PR #323: - core2-duo-p7350: launch Q3'08 per ARK 36750 -> 2008-08-01 (was 2008-12-01) - core2-duo-p8800: launch Q2'09 per ARK 40380 -> 2009-04-01 (was 2009-07-01) - core2-duo-u7500: Socket M (PBGA479) Merom part per ARK 36931; date -> 2007-04-27 (was 2009-03-01), moved to 2007/ - core2-duo-u7700: Socket M Merom original per ARK 33920 lineage; socket null -> BGA479, date -> 2007-12-27 (was 2008-12-01), moved to 2007/ - core2-duo-e8135: TDP null -> 44W per TechPowerUp - core2-duo-e8435: TDP null -> 44W (Mar 2009 stepping) per TechPowerUp/technical.city - xeon-3040: Conroe SL9TW per ARK 27203 / Wikipedia -> 2006-09-26 (was 2009-11-01), moved to 2006/ - xeon-3050: Conroe SL9TY per ARK 27204 / Wikipedia -> 2006-09-26 (was 2009-02-01), moved to 2006/ celeron-d-330 and core2-duo-p7450 left unchanged: source-verified as already correct (330 genuinely shipped in both Socket 478 and LGA775 variants at identical clock/TDP/date; p7450 already within tolerance). Refs #296
Regenerated via 'python -m app.dump' (TechEngine) against a fresh scratch database seeded from this worktree, rebased onto the current develop. Reflects the 8 corrected Intel CPU records plus the resulting population-relative score percentile updates. Refs #296
Seungpyo1007
force-pushed
the
Seungpyo1007/intel-slug-recheck
branch
from
September 29, 2026 19:53
3e2285f to
59e8ff4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fresh-look, source-verified pass over the residual ambiguous Intel CPU slugs that PR #323 left unresolved. For each I went beyond the Wikipedia rows that disagreed and cross-checked Intel ARK (via archived ARK snapshots), the Wikipedia Xeon/Celeron model-number lists, and TechPowerUp / technical.city.
Resolved and fixed (8):
Files for the four date-corrected parts were moved into their correct year folders (u7500/u7700 -> 2007/, xeon-3040/3050 -> 2006/) per the
data/cpu/<mfr>/<year>/<segment>/<slug>.jsonconvention.Source-verified as genuinely fine, left unchanged (2):
330shipped in both Socket 478 (SL7KZ/SL7NV/... ) and LGA775 (SL8HL) at identical 2.667 GHz / 73 W / June 24 2004. The stored LGA775 is a valid variant; the dual-socket ambiguity is real hardware, not a mistake.Testing
python -m app.validate-> passes.python -m app.dump(TechEngine) against a fresh scratch DB seeded from this worktree; last commit carries the regeneratedsite/publicdump (the 8 records plus population-relative score-percentile updates).Closes #296