Landing: 604a45f74909

Project / Subsystem

gcc / gcc/tree-optimization

Date

2026-06-18

Author

Andrew MacLeod

Commit

604a45f74909987929eb77dfc1119fa94aedb1e1

Source

github

Perf win

Yes

Breaking

No

All attributes

project
gcc
subsystem
gcc/tree-optimization
patch_id
commit_hash
604a45f74909987929eb77dfc1119fa94aedb1e1
source_type
github
headline
Ranger optimization cache uses two timestamps
tldr
Ranger optimization cache distinguishes between value storage and calculation times for better cache invalidation.
author
Andrew MacLeod
outcome
committed
performance_win
true
breaking_change
false
series_id
series_parts
[]
tags
  • optimization
  • gcc
  • compiler
discussion_id_link
bugzilla_pr
date
2026-06-18T00:00:00.000Z

The Ranger optimization pass’s caching mechanism has been updated to use two distinct timestamps: one for when a value was last stored and another for when it was last calculated. This allows the compiler to differentiate between a value that was recalculated but unchanged, and one that truly changed. This finer-grained tracking improves the cache’s accuracy and efficiency by preventing unnecessary recalculations when a value’s computed result remains the same.