https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Richard Biener from comment #4) > It might make sense to provide targets a means to opt-out of CTF/BTF support > and thus diagnose -gctf as unsupported on them. In the short-term, I've got fixes for the invocation-related issues, which I'll commit today. A new debug format is clearly a vast undertaking - requiring buy-in from many organisations - in the case of Darwin, it will mean amendment to ld64 (to recognise and deal with relocation-less offsets) and dsymutil (to handle linking the debug) and then lldb / gdb / backtrace etc. to deal with common consumers. Releases for these tools are controlled by Apple - clearly one can self-build hacked version, but that's extremely unlikely to reach the larger majority of Darwin/macOS developers. == for opt out. It would be a simple matter to add a driver self-spec to reject '-gctf' and '-gbtf' (which can be arranged to give an error) and then, I guess, to add opt-out to the testsuite selectors? In any event, opt-out is likely the only sensible action for older platforms where "rebuild the world" is not an option; how can this interoperate with existing libraries etc. using DWARF debug?
