https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245
--- Comment #10 from Rich Felker <bugdal at aerifal dot cx> --- Since musl 1.1 introduced unconditional setup of thread pointer, the previously-reported consequence is no longer relevant with modern versions. However it's still either a missed optimization (emitting useless canary load despite the fact that there's no code to check the canary) or missed hardening (checking canary before leaving via a noreturn function) and thus seems interesting still.
