https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79341
--- Comment #68 from Dominik Vogt <vogt at linux dot vnet.ibm.com> ---
Okay, that fixes the test failure, but the addresses further up in the
backtrace are still bad, e.g.
#0 0x10008d2 in NullDeref
#1 0x1000759 in main
#2 0x3fffce23069 in
#3 0x10007d5
Maybe it's not worth it to knock a workaround together when a real fix is
preferrable. It's probably acceptable to wait for an upstream fix.
