https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105708
--- Comment #7 from Keno Fischer <keno at juliacomputing dot com> --- I'm probably talking in circles at this point, but let me try just one more time. I just want to clarify that I understand that this is not technically a libgcc bug. But it's not really an rr bug either. Existing hardware already barely supports rr and we're still working with a number of silicon vendors to address microarchitecture bugs that are causing issues. We'll also keep advocating for hardware support for ll/sc emulation/trapping, but as you can imagine that's a big lift. It's not a matter of rr just fixing some code - the hardware support required for this does not currently exist. These limitations are proactively communicated to the user and there are appropriate error messages for unsupported situations (e.g. use of a broken microarchitecture or recording of an application that used ll/sc). I was hoping by making this change in libgcc we could increase the number of situations where rr does work, without putting significant extra burden on the distribution maintainers. That said, if this really is a hard WONTFIX here, then we'll work with the distribution maintainers to start carrying a libgcc patch as necessary :(. It's gonna be messy and I'm not looking forward to it, but I don't really know what else to say to make my case here.
