https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91420
Alexandre Oliva <aoliva at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |aoliva at gcc dot
gnu.org
--- Comment #12 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
Created attachment 62624
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=62624&action=edit
candidate patch
Mine.
I'm still testing this patch, but it appears to address as many of the reported
problems as I could still trigger with a gcc-14 toolchain, where I first hit
the problem and where I started looking for fixes.
I'm not very happy with this simplistic solution, but since the compiler has no
clue about how much margin there is in the whole program, or where the access
is going to land in it, it's hard to do better.
An alternative I'm considering is a parameter that could enable users to tell
the compiler how conservative to be. Would that be preferred?
Any other thoughts or recommendations?
