Page MenuHomeFreeBSD

libc: stop trying to create __<syscall> symbols
ClosedPublic

Authored by brooks on Aug 1 2025, 12:35 PM.
Tags
None
Referenced Files
F175558066: D51668.id159541.diff
Sun, Oct 11, 4:54 PM
F175557764: D51668.id159847.diff
Sun, Oct 11, 4:52 PM
F175555465: D51668.diff
Sun, Oct 11, 4:33 PM
Unknown Object (File)
Sun, Oct 11, 9:00 AM
Unknown Object (File)
Tue, Oct 6, 12:01 AM
Unknown Object (File)
Mon, Oct 5, 11:52 PM
Unknown Object (File)
Mon, Oct 5, 11:02 PM
Unknown Object (File)
Sat, Oct 3, 3:19 AM
Subscribers

Details

Summary

When we switched to an interposing table (commit 8495e8b1e9e1) for
cancelation points we stopped having concrete implementations of
<syscall> and instead use sys_<syscall> and __thr_<syscall>.
These entries of the form:

weak_reference(sys_<syscall>, __<syscall>);

seem to be intended to preserve these symbols, but they have no effect
as __sys_<syscall> isn't defined in the translation units in question.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I have half a memory of this pattern being added to the mix as a compat bridge when moving away from libcR... but it's clear they'd have no effect now

This revision is now accepted and ready to land.Aug 1 2025, 5:50 PM