emacs-31 f532313220b: ; DUMP_RELOCATION_ALIGNMENT comment fix

Paul Eggert <[email protected]> Thu, 16 Jul 2026 14:02:04 -0400 (EDT)
Newsgroups gmane.emacs.diffs
Message-ID <[email protected]>
branch: emacs-31
commit f532313220b61c2d8448d9d99c8cfa5e8046c9b6
Author: Paul Eggert <[email protected]>
Commit: Paul Eggert <[email protected]>

    ; DUMP_RELOCATION_ALIGNMENT comment fix
    
    * src/pdumper.c (DUMP_RELOCATION_ALIGNMENT):
    Fix comment to match relocation alignment requirements.
    Backported from master branch commit
    3c0bc3f2ebe54007905f5f81f0418de7fefe8076.
---
 src/pdumper.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/src/pdumper.c b/src/pdumper.c
index f20d42a07f9..7415ba7a3bb 100644
--- a/src/pdumper.c
+++ b/src/pdumper.c
@@ -269,9 +269,10 @@ enum
   {
    DUMP_RELOC_TYPE_BITS = 5,
 
-   /* Minimum alignment required by dump file format.  Although this can
-      be any integer power of 2 up to alignof (Lisp_Alignment),
-      larger values help dump_reloc_set_offset support larger offsets.
+   /* Minimum alignment required by dump file format.  Lisp_Objects and raw
+      pointers can both be relocated, so this can be any integer power of 2
+      up to min (alignof (Lisp_Object), alignof (void *)).
+      Larger values help dump_reloc_set_offset support larger offsets.
       The fix for bug#44531 was discovered late during Emacs 31 development,
       so on Emacs 31 the value is 4 except on hosts where 4 is known to fail.
       The only known failure is m68k a.out, so work around the problem