http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60213
--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> --- (In reply to hubert.vansteenhuyse from comment #3) > Of course it is, the example is merely a pseudo code to make clear what > happened. That's my point, pseudo-code is useless, if we can't reproduce the issue it doesn't make it clear at all what is going on. Compiler bugs (in case this is one) often have unpredictable symptoms. > Don't worry about it, if someone else ever reports it then it might be worth > to take a closer look to it. But we will have no idea that it is related. If you can post a valid, self-contained example that exhibits the issue (preferably with a supported version of gcc, so at least 4.7), that would be helpful. Otherwise I'll just close the PR.
