Andy Wingo says:
> I once did some painful CVS bisection, which for the compiler flags I was
> using brought it back to the introduction of the inline keyword in 2002
> or something.
Perhaps you're on to something -- the "inline" business reminded me of
the old pstate bug where a variable was being optimized off the stack
causing premature gc, or something like that. So, I rebuilt guile using
-g3 and not -O2, and the build ran to completion! Unfortunately, it's still
not right; guile doesn't segfault but I get:
/home/bil/test/ bin/guile
Backtrace:
In unknown file:
?: 130* [syntmp-gen-syntax-1074 #(syntax-object # #) #(syntax-object # #)
...]
?: 131 (if (syntmp-id?-115 syntmp-e-1110) (let* (#) (let* # #)) ...)
...
?: 132 [call-with-values #<procedure #f ()> #<procedure #f #>]
?: 133 (@call-with-values (producer consumer))
?: 134* [#<procedure #f ()>]
?: 135* [syntmp-gen-syntax-1074 #(syntax-object # #) #(syntax-object begin
#) ...]
?: 136 (if (syntmp-id?-115 syntmp-e-1110) (let* (#) (let* # #)) ...)
...
?: 137 (if # # #)
?: 138* [syntmp-ellipsis?-160 #(syntax-object begin (# # # #))]
?: 139 (and # #)
...
?: 140 [syntmp-free-id=?-138 #(syntax-object begin #) #(syntax-object ...
#)]
?: 141 (and (eq? # #) (eq? # #))
?: 142* [eq? ...
?: 143* (let* ((syntmp-x-885 syntmp-i-883)) (let* (#) (if # #
syntmp-e-886)))
?: 144 (let* (#) (if # # syntmp-e-886))
?: 145* (if # # syntmp-x-885)
?: 146* [syntmp-syntax-object?-101 #(syntax-object begin (# # # #))]
?: 147 (and (vector? syntmp-x-1008) (= (vector-length syntmp-x-1008) 3)
...)
?: 148* [= ...
?: 149* (vector-length syntmp-x-1008)
<unnamed port>: In expression (vector-length syntmp-x-1008):
<unnamed port>: Stack overflow
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
