https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63630
--- Comment #7 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- (In reply to Eric Gallager from comment #6) > gcc-5 branch is closed; is this bug still valid for newer branches? Reload flaws are usually very "instable" w.r.t. to the test case(s) that thrigger them. I really can't tell whether the artefact is still present on source level or has already been fixed or been supersed by re-design. For a definite answer, one would have to analyse the issue with a gcc version + test case that triggers the bug and then track the respective source and how it changed in the remainder...
