https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109443
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #11) > And I don't see any code generation changes on the #c0 testcase with added > #include <vector> with the patch. Yes, that's because we cannot disambiguate the call against a restrict qualified memory access. But otherwise it "works". Note maybe the restrict qualification isn't the best representation since it doesn't capture the value will die upon function return (does it? I gues the DTOR if any will run in caller context and thus stores to it are not necessarily "dead"). It's on my list of things to do to investigate adding "'restrict' support" to calls for GCC14.
