aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2021-11-23 14:44:45 +0200
committerEli Zaretskii2021-11-23 14:44:45 +0200
commitbdb489ad5dd81c8aef8ada8940f6981034dfaf82 (patch)
treeb7108c93aabd6c7cf79416087b50cc0eb87d224e
parentb4fb381d8d7e866676650a7283ac6d873838c49f (diff)
downloademacs-bdb489ad5dd81c8aef8ada8940f6981034dfaf82.tar.gz
emacs-bdb489ad5dd81c8aef8ada8940f6981034dfaf82.zip
; * etc/DEBUG: Adjust instructions for libgccjit reproducer.
-rw-r--r--etc/DEBUG7
1 files changed, 4 insertions, 3 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index 555370588fe..ced6a92d711 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -591,9 +591,10 @@ If you cannot figure out the cause for the problem using the above,
591native-compile the problematic file after setting the variable 591native-compile the problematic file after setting the variable
592'comp-libgccjit-reproducer' to a non-nil value. That should produce a 592'comp-libgccjit-reproducer' to a non-nil value. That should produce a
593file named ELNFILENAME_libgccjit_repro.c, where ELNFILENAME is the 593file named ELNFILENAME_libgccjit_repro.c, where ELNFILENAME is the
594name of the problematic .eln file, in the same directory where the 594name of the problematic .eln file in the same directory where the .eln
595.eln file is produced. Then attach that reproducer C file to your bug 595file is produced, or a file repro.c under your ~/.emacs.d/eln-cache
596report. 596(which one depends on how the native-compilation is invoked). Then
597attach that reproducer C file to your bug report.
597 598
598** Following longjmp call. 599** Following longjmp call.
599 600