On 01/12/18 4:36 AM, Alfred M. Szmidt wrote:
Emacs:
~/emacs/src $ python3 ~/gen-changed-entities.py
f1ea2b9e6b63593f5919f60a68a9e19026756ac4
0e484c66fd63877230c3dfa97f2ce9dda71ad88b
[...]
[_REGEX_RE_COMP ||
_LIBC][_LIBC][_LIBC][RE_ENABLE_I18N][RE_ENABLE_I18N][RE_ENABLE_I18N][!
_LIBC][RE_ENABLE_I18N][!(RE_ENABLE_I18N)][!(RE_ENABLE_I18N)][!
_LIBC][!(RE_ENABLE_I18N)][_LIBC][RE_ENABLE_I18N][!(RE_ENABLE_I18N)][_LIBC][!(RE_ENABLE_I18N)][RE_ENABLE_I18N](if):
Modified.
[... and a bunch of what seems to be unrelated changes and files?]
The singleton change is:
commit 0e484c66fd63877230c3dfa97f2ce9dda71ad88b (HEAD -> master, origin/master,
origin/HEAD)
Author: Gemini Lasswell <[email protected]>
Date: Sun Oct 14 12:12:04 2018 -0700
Keep a stack reference to bytecode objects being executed (Bug#33014)
* src/eval.c (Ffuncall): Make local variable 'fun' volatile.
* test/src/eval-tests.el
(eval-tests-byte-code-being-evaluated-is-protected-from-gc):
Add regression test for Bug#33014.
(eval-tests-33014-var): New variable.
(eval-tests-33014-func, eval-tests-33014-redefine): New functions.
I've fixed this in my branch. It now says (DEFUN): Modified, which is
not precise but close enough since it would be a lot harder to
preprocess that macro to find the actual function in question.
Glibc:
~/glibc $ python3 ../gen-changed-entities.py
c6a5bdc18979c09c7a2a9cf23fff8ac5781962ae
ce7387cc250a408d3fbb7a6fff7ad4d977166b00
2018-11-29 H.J. Lu <[email protected]>
COMMIT: ce7387cc250a408d3fbb7a6fff7ad4d977166b00
* elf/dl-exception.c: Modified.
(_itoa.h): New.
The singleton change is:
commit ce7387cc250a408d3fbb7a6fff7ad4d977166b00
Author: H.J. Lu <[email protected]>
Date: Thu Nov 29 20:03:46 2018 -0800
elf/dl-exception.c: Include <_itoa.h> for _itoa prototype
Tested with build-many-glibcs.py.
* elf/dl-exception.c: Include <_itoa.h>.
This now says:
* elf/dl-exception.c: Modified.
(_ita.h): Include file.
I'll put a patch out for review on libc-alpha soon.
Siddhesh
