On 10/7/20 10:43 AM, Andrew MacLeod via Gcc-patches wrote: > When I broke r11-3684 temporarily yesterday, it was fixed in the next > commit. > > But it does mean that for anyone bisecting a problem, theres a broken > commit. > > Is there a blessed way to fix that? or does it stay broken forever? > All I need to do is change a single line in gimple-range.h... > > or do we just let sleeping dogs lie?
Rewriting history isn't allowed or advisable. Yea, it sucks that there's a commit in the tree that causes problems, but rewriting history would likely have a wider impact than bisection problems related to that commit. So leave it as-is. jeff
