Mark Mitchell wrote:
No, I don't think we know. There's speculation in the PR trail, but that's it. I'd appreciate it if you were able to investigate further, but I think I'd best just accept that this will not be fixed for 4.2.0.
Or revert the patch that revealed the bug, or apply Richard Guenther's other patch to work around it?
Jason
