Comment 41 for bug 1890435

The extra checks that are enabled trigger the same issues I was seeing with gcc-snapshot (maybe they have it enabled as well?).

/root/qemu-5.0/linux-user/syscall.c: In function ‘do_setsockopt’:
/root/qemu-5.0/linux-user/syscall.c:1935:17: note: non-delegitimized UNSPEC UNSPEC_PIC_SYM (1) found in variable location
 1935 | static abi_long do_setsockopt(int sockfd, int level, int optname,
      | ^~~~~~~~~~~~~
...
/root/qemu-5.0/linux-user/syscall.c: In function ‘do_syscall1.constprop’:
/root/qemu-5.0/linux-user/syscall.c:7674:17: note: non-delegitimized UNSPEC UNSPEC_PIC_SYM (1) found in variable location
 7674 | static abi_long do_syscall1(void *cpu_env, int num, abi_long arg1,
      | ^~~~~~~~~~~
/root/qemu-5.0/linux-user/syscall.c:7674:17: note: non-delegitimized UNSPEC UNSPEC_PIC_SYM (1) found in variable location
/root/qemu-5.0/linux-user/syscall.c:7674:17: note: non-delegitimized UNSPEC UNSPEC_PIC_SYM (1) found in variable location
...

I see many of those, but all are only "note:" level and when searching for the actual issue I now find this more verbose output (next comment for readability):