https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118473
--- Comment #4 from jbeulich at suse dot com ---
(In reply to Andrew Pinski from comment #1)
> Does this happen only for x86_64 or also for aarch64?
As per a quick experiment - yes, same issue there. Not surprising considering
that both targets
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118473
--- Comment #3 from Andrew Pinski ---
Also the bad relocation is recorded as pr 32434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118473
--- Comment #2 from Andrew Pinski ---
Also do you have a simple Testcase?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118473
--- Comment #1 from Andrew Pinski ---
So I think __stack_chk_guard is special and handled in the backend rather than
the middle end so the visibility will need to be handled in the backend.
Does this happen only for x86_64 or also for aarch64?
