https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54488
Evgeniya Maenkova <evgeniya.maenkova at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |evgeniya.maenkova at gmail dot com --- Comment #1 from Evgeniya Maenkova <evgeniya.maenkova at gmail dot com> --- Could you please clarify this bug status? (As I can see PR46590 you applied some patch that fixes memory issues in Jan of 2014). As I can see from the code (I'm very newbie, sorry for mistakes) there are the structures which keep the information about memory accesses in the whole function (for all the loops). When I read you comment in this bug I started to think there is some possibility to keep the only information about individual loop (which I could try to implement). However, the comment in PR46590 says you meant something different.