Re: next_char inlining (was: Re: M4 1.4.10b [beta] released)

2008-02-29 Thread Bruno Haible
| The speed-relevant code is only the case for INPUT_CHAIN. I added the one | for INPUT_STRING because it may be useful it situations I don't know of. And here is, for completeness, the handling of INPUT_FILE. It requires the modules freadahead, freadptr, freadseek from gnulib. No speed improvemen

Re: next_char inlining

2008-02-29 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 2/29/2008 12:33 AM: |> | + if (curr_quote.len1 == 1 && curr_quote.len2 == 1 && !input_change |> | + && isp) |> |> Not quite right. The condition here needs to be that quote_age is |> non-zero (certain

Re: next_char inlining

2008-02-29 Thread Eric Blake
Eric Blake byu.net> writes: > | > |> ~ I'm also considering adding a placeholder input block that always results > |> in CHAR_EOF, so that isp is guaranteed to be non-null and we have one less > |> branch in this loop. > | > | Tried this already (see attached patch). It does not provide a noticea