On 23/04/2020 12:21, Kwok Cheung Yeung wrote:
I agree that not generating the problematic code in the first place is the better approach. Does that mean we can now remove libgcc/config/gcn/unwind-gcn.c completely?
That was added for the benefit of libgfortran, not C++. It's used by the backtrace code called from the stop handler, among other places, and I don't believe there was another workaround for that (without adding extra config checks to libgfortran).
I had not got to Thomas's patch yet, so I hadn't noticed they solved the same problem.
It probably is better to use Thomas's patch. I'm just worried that it'll catch me out when we do implement this stuff, in a way that the stub would not.
Andrew
