MétaCan
Menu
Back to cohort
Record W4416429953 · doi:10.1109/iiswc66894.2025.00022

The Curious Case of Global Stable Loads

2025· article· W4416429953 on OpenAlexaff
Shagnik Pal, Jeeho Ryoo, Lizy K. John

Bibliographic record

Venuenot available
Typearticle
Language
FieldComputer Science
TopicParallel Computing and Optimization Techniques
Canadian institutionsBecton Dickinson (Canada)
Fundersnot available
KeywordsCompilerCacheSpec#Microarchitecturex86SpeedupFetchExecution time

Abstract

fetched live from OpenAlex

A recent study presented an interesting statistic that about one-third and up to two-thirds of the load instructions in many x86 programs are redundant. These redundant loads fetch the same value from the same address throughout the execution of the program, and are called global stable loads (GSLs). We explore the behavior of GSLs across different architectures, compilers, and compiler optimizations. We also study GSLs in emerging ML workloads that are not explored in prior work. Our characterization of SPEC programs reveal a high locality in GSLs, that only 4.2-5.2% of static GSLs are responsible for 90-95% of the dynamic GSLs. We identify the reasons behind these dominant static GSLs, and posit that many of these GSLs are identifiable by the compiler prior to execution.In contrast to using a purely microarchitectural solution to eliminate GSLs, we consider a compiler-hardware co-designed solution wherein the compiler marks the likely stable loads, and the microarchitecture uses a small and fast cache to service these loads quickly and efficiently. We achieve a maximum speedup up to 7.43% for SPEC Float programs, and attain an energy reduction of 12.95% for the L1-D cache. We achieve these results using minimal hardware and without the need for a complex microarchitectural mechanism, yet the results are similar to state-of-the-art solutions.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.010
Threshold uncertainty score0.035

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.005
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0020.002
Scholarly communication0.0020.005
Open science0.0010.002
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0100.003

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.010
GPT teacher head0.290
Teacher spread0.280 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2025
Admission routes1
Has abstractyes

Explore more

Same topicParallel Computing and Optimization TechniquesFrench-language works237,207