https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95052
--- Comment #5 from Krzysztof Nowicki <krzysztof.a.nowicki+gcc at gmail dot com> --- (In reply to Martin Sebor from comment #4) > I don't expect the commit above to have changed anything for the latter > form, and I would expect each back end to choose the same optimal code to > emit in both cases. So I don't think the commit above is a regression; it > just exposed an inefficiency that was already present. Yes, from the implementation point of view I agree - the missed optimization was there all the time and this commit exposed it in one more use case, where it wasn't seen before. However from the point of view of an application developer on an embedded system, who has developed it with some memory constraints in mind, a sudden increase of memory usage, possibly causing an OOM since the memory budget on this system is very tight (legacy platform), just by upgrading the compiler is a regression.
