summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorDirk Herrmann <dirk@dirk-herrmanns-seiten.de>2000-12-28 16:06:56 +0000
committerDirk Herrmann <dirk@dirk-herrmanns-seiten.de>2000-12-28 16:06:56 +0000
commitfcba9b58c677407263282a4028f55c33151d2ca5 (patch)
treebfaa1e9eb744f45ddd2e4496a1468d0edecfb312 /HACKING
parent23a62df4fea25cfaa41382f283aa8b2411d7015b (diff)
downloadguile-fcba9b58c677407263282a4028f55c33151d2ca5.tar.gz
* Get rid of the annoying variable-gets-clobbered-by-longjmp warning.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING9
1 files changed, 2 insertions, 7 deletions
diff --git a/HACKING b/HACKING
index 69258c4af..17f3fd7bf 100644
--- a/HACKING
+++ b/HACKING
@@ -130,13 +130,8 @@ make-stds.texi.
- The Guile tree should compile without warnings under the following
GCC switches, which are the default in the current configure script:
- -O2 -Wall -Wpointer-arith -Wmissing-prototypes The only warnings
-which can be tolerated are those about variables being clobbered by
-longjmp/vfork in eval.c. The variables in question are critical to
-the interpreter's performance; as far as I can tell, it is
-difficult/annoying to avoid these warnings without slowing the system
-down substantially. (If you can figure out a good fix, I'd be happy
-to see it.)
+
+ -O2 -Wall -Wpointer-arith -Wmissing-prototypes
Note that the warnings generated vary from one version of GCC to the
next, and from one architecture to the next (apparently). To provide