Rob Browning <[EMAIL PROTECTED]> writes:
>
> If we're going to implement string-every in C, then that's the best we
> can do right now, and from looking at the output of srfi-13.s via
> -save-temps (presuming I'm reading the x86 assembly right) newer gcc's
> optimize that call to a jmp.

I wouldn't worry, unless everything else in the eval path is optimized
that way too.  Even then it's relying on a new enough gcc.


_______________________________________________
Bug-guile mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-guile

Reply via email to