aboutsummaryrefslogtreecommitdiffstats
path: root/java/debug.sh
diff options
context:
space:
mode:
authorMattias EngdegÄrd2023-08-28 11:13:10 +0200
committerMattias EngdegÄrd2023-09-18 20:06:01 +0200
commit861f9cb78370e2b78f852e5ccde9b63c94486ca8 (patch)
tree212ba6f4cf9d1df5ba6887a322e79cbb0d0f10cb /java/debug.sh
parent146bd41ddef21a19634e2b90db4bfb619a2091b2 (diff)
downloademacs-861f9cb78370e2b78f852e5ccde9b63c94486ca8.tar.gz
emacs-861f9cb78370e2b78f852e5ccde9b63c94486ca8.zip
Don't use pointer arithmetic for untagging Lisp values (bug#65491)
* src/lisp.h (XUNTAG): Instead of casting a Lisp value to char * and subtracting the tag, cast it to a suitable integral type and work on that. This should result in identical or at least equivalent code, except that it avoids potential problems arising from the restrictions on pointer arithmetic in C. In particular, a null pointer can be neither an operand in nor the result of pointer arithmetic. C compilers know this and would, prior to this change, optimise XUNTAG(obj, Lisp_Int0, mytype) != NULL to 1. This means, for example, that make_pointer_integer and XFIXNUMPTR could not be entrusted with null pointers, and next_vector in alloc.c was unsafe to use.
Diffstat (limited to 'java/debug.sh')
0 files changed, 0 insertions, 0 deletions