https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119996
Nathaniel Shead <nshead at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |15.2 Ever confirmed|0 |1 CC| |nshead at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |nshead at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2025-04-29 Keywords| |accepts-invalid, wrong-code --- Comment #1 from Nathaniel Shead <nshead at gcc dot gnu.org> --- Confirmed. This applies to inline object references as well. The root cause seems to be that because a reference is potentially-constant, we avoid streaming its TU-local value, and never end up marking it as an exposure. I think we should be marking it an exposure at that point.