On Mon, 7 Jul 2025 at 13:03, Collin Funk wrote:
> Martin D Kealey writes:
> > it's SLOW.
Any comments on this point?
It seems like the main causes of inadequate speed are:
(1) Lack of parallelism.
(2) A monolithic probe-test-result cache structure, that's either "all
valid" or "all discarded"
On Sun, Jul 6, 2025, at 10:25 PM, Martin D Kealey wrote:
> To help me find bugs in a range of projects, I have a wrapper around gcc
> that forces -Werror -pedantic.
>
> [...]
>
> A significant source of detection failures is that the probes assume that
> K&R function declarations (without parameter
Martin D Kealey writes:
>
> At this point I'm beginning to question the value of autoconf for "general
> use". I'm sure it's still useful for corner cases, but it was conceived for
> a different world, and assumptions made back then have become problems now.
>
> And it's SLOW. On my fairly old com
To help me find bugs in a range of projects, I have a wrapper around gcc
that forces -Werror -pedantic.
I expect to get a lot of errors during builds - that's the point - but what
I didn't expect was for autoconf to be broken.
The main problem is that autoconf fails to recognize a range of standar
On 7/6/25 12:13 AM, Martin D Kealey wrote:
diff --git a/bashline.c b/bashline.c
index fb8aeea20..181585c5b 100644
--- a/bashline.c
+++ b/bashline.c
@@ -4142,7 +4142,7 @@ vi_advance_point (void)
}
}
#else
-rl_point++:
+rl_point++;
#endif
return point;
}
Thanks for the
