Page MenuHomeFreeBSD

tip: Fix pointer-vs-integer confusion
ClosedPublic

Authored by jrtc27 on Jun 8 2021, 3:07 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jan 25, 7:36 PM
Unknown Object (File)
Sat, Jan 25, 1:10 PM
Unknown Object (File)
Fri, Jan 24, 5:24 PM
Unknown Object (File)
Dec 21 2024, 4:04 PM
Unknown Object (File)
Nov 10 2024, 4:42 PM
Unknown Object (File)
Oct 24 2024, 3:00 AM
Unknown Object (File)
Oct 1 2024, 6:45 AM
Unknown Object (File)
Sep 27 2024, 12:18 AM
Subscribers
None

Details

Summary

Currently IREMOTE assumes that every value is (initially) a pointer to a
long. This is true for NUMBERs, but false for STRINGs, which are instead
pointers to pointers, though on ILP32 and LP64 systems these happen to
have the same representation, but this is still a strict aliasing
violation, and of course breaks on systems where the representations are
not the same, such as CHERI. We do not currently have any BOOLs (short,
curiously) or CHARs used with IREMOTE, though the code should not be
relying on that.

This removes the unused setaddress macro, and the now-unused address
macro due to the above issue.

Obtained from: CheriBSD

Diff Detail

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