You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building FreeBSD kernel modules with a standard LLVM 17.0.6 toolchain and -fstack-protector results in them containing R_X86_64_REX_GOTPCRELX relocations (for __stack_chk_guard). These are unloadable, because this relocation type isn't handled by the FreeBSD kernel loader.
There has been discussion about upstreaming this into LLVM in D113443. It appears there was a consensus to submit once a comment was added. I'm filing this issue so we can get that patch submitted in some appropriate form.
Also, please see #60116, but note that the current !TM.getTargetTriple().isOSFreeBSD() condition in TargetLoweringBase::insertSSPDeclarations still overrules that fix. Thus, -fdirect-access-external-data is not a solution here.
Building FreeBSD kernel modules with a standard LLVM 17.0.6 toolchain and
-fstack-protector
results in them containing R_X86_64_REX_GOTPCRELX relocations (for__stack_chk_guard
). These are unloadable, because this relocation type isn't handled by the FreeBSD kernel loader.This was addressed internally within FreeBSD already via freebsd/freebsd-src@9a4d48a645a7a.
There has been discussion about upstreaming this into LLVM in D113443. It appears there was a consensus to submit once a comment was added. I'm filing this issue so we can get that patch submitted in some appropriate form.
cc @DimitryAndric @adalava
The text was updated successfully, but these errors were encountered: