Skip to content

Conversation

@zhangskz
Copy link
Member

This data structure is better for cases where writes are rare and reads common. When this warning path is it, the writes only occur exactly once per CVE-affected type, and reads occur once per every parse of those types.

Broadly people sensitive by this performance concern should really regen their gencode, but this should help take the edge off of people who first upgrade to 4.x and then look to incrementally regen any ancient gencode.

Fixes #23963

PiperOrigin-RevId: 819238880

Cherry-pick of c131253

This data structure is better for cases where writes are rare and reads common. When this warning path is it, the writes only occur exactly once per CVE-affected type, and reads occur once per every parse of those types.

Broadly people sensitive by this performance concern should really regen their gencode, but this should help take the edge off of people who first upgrade to 4.x and then look to incrementally regen any ancient gencode.

Fixes #23963

PiperOrigin-RevId: 819238880
@zhangskz zhangskz requested a review from a team as a code owner October 14, 2025 17:27
@zhangskz zhangskz requested review from esrauchg and googleberg and removed request for a team October 14, 2025 17:27
@zhangskz zhangskz enabled auto-merge (squash) October 14, 2025 17:31
@zhangskz zhangskz merged commit e55224c into 33.x Oct 14, 2025
222 checks passed
@zhangskz zhangskz deleted the cp-pre22-warn-fix branch October 14, 2025 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants