Home
last modified time | relevance | path

Searched hist:"93898 f2b2d3339874ac31d935b8c67c67b6929ba" (Results 1 – 1 of 1) sorted by relevance

/freebsd/sys/sys/
H A Dprocfs.hdiff 93898f2b2d3339874ac31d935b8c67c67b6929ba Sun Sep 14 18:52:42 CEST 2008 Marcel Moolenaar <marcel@FreeBSD.org> Widen psaddr_t from uintptr_t to uint64_t. This results in an
ABI change on ILP32 platforms and relating to events. However
it's harmless on little-endian ILP32 platforms in the sense
that it doesn't cause breakages. Old ILP32 thread libraries
write a 32-bit th_p and new thread libraries write a 64-bit
th_p. But due to the fact that we have an unused 32-bit data
field right after th_p and that field is always initialized to
zero, little-endian ILP32 machines effectively have a valid
64-bit th_p by accident. Likewise for new thread libraries and
old libthread_db: little endian ILP32 is unaffected.

At this time we don't support big-endian threaded applications
in GDB, so the breakage for the ILP32 case goes unnoticed.
diff 93898f2b2d3339874ac31d935b8c67c67b6929ba Sun Sep 14 18:52:42 CEST 2008 Marcel Moolenaar <marcel@FreeBSD.org> Widen psaddr_t from uintptr_t to uint64_t. This results in an
ABI change on ILP32 platforms and relating to events. However
it's harmless on little-endian ILP32 platforms in the sense
that it doesn't cause breakages. Old ILP32 thread libraries
write a 32-bit th_p and new thread libraries write a 64-bit
th_p. But due to the fact that we have an unused 32-bit data
field right after th_p and that field is always initialized to
zero, little-endian ILP32 machines effectively have a valid
64-bit th_p by accident. Likewise for new thread libraries and
old libthread_db: little endian ILP32 is unaffected.

At this time we don't support big-endian threaded applications
in GDB, so the breakage for the ILP32 case goes unnoticed.