https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110137
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 2 Aug 2023, redi at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110137 > > --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- > Why would that depend on this new option? It's a requirement of the standard, > it has to be true always. And GCC already assumes this. Note we don't make an exception for pointers passed to deallocation - we're using the info mainly for memory access disambiguation and rely on the deallocation call itself to be a barrier for code motion here.
