https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115636
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
Status|NEW |ASSIGNED
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Going to implement something for isolate-paths. It might not be exactly what
was expecting here due it might be using a trap rather than 0.
> According to the behavior of gcc
Note this is statement is not exactly "correct" it is just the behavior for gcc
currently for this undefined behavior.
Note I have a straw poll going on which behavior we should do (maybe even by
default):
https://gcc.gnu.org/pipermail/gcc/2024-June/244213.html
