https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114839
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Hmm, I wonder why freebsd needs to be different from every most other targets
though here:
```
config/alpha/elf.h:#define LINK_EH_SPEC "%{!static|static-pie:--eh-frame-hdr} "
config/arc/linux.h:#define LINK_EH_SPEC "--eh-frame-hdr "
config/dragonfly.h:#define LINK_EH_SPEC "--eh-frame-hdr"
config/freebsd.h:#define LINK_EH_SPEC "%{!static|static-pie:--eh-frame-hdr} "
config/fuchsia.h: "%{!no-eh-frame-hdr: --eh-frame-hdr}" \
config/gnu-user.h:#define LINK_EH_SPEC "%{!static|static-pie:--eh-frame-hdr} "
config/netbsd.h:#define LINK_EH_SPEC "%{!static|static-pie:--eh-frame-hdr} "
config/openbsd.h:#define LINK_EH_SPEC "%{!static|static-pie:--eh-frame-hdr} "
config/sol2.h: --eh-frame-hdr to create the required .eh_frame_hdr sections.
*/
config/sol2.h:#define LINK_EH_SPEC "%{!static|static-pie:--eh-frame-hdr} "
```
Is it the case that unwinder from LLVM needs a .eh_frame_hdr for static
binaries while GCC's libgcc one does not?
