Browse Source
I noticed that exception_print_same is only used in a single spot, and it seemed to be better as an operator!= method attached to gdb_exception. Regression tested on x86-64 Fedora 34.users/ARM/efi-aarch64-support-binutils
4 changed files with 18 additions and 18 deletions
Loading…
Reference in new issue