Re: Time to merge scratch/correct-warning-pos into master, perhaps?

[Gregory Heytings]

> > I'd like to see the results from elisp-benchmarks with and without this 
> > patch set, please.
>
> In my experience, the elisp-benchmarks are very much not representative 
> of actual elisp usage, and I have done quite some benchmarking for other 
> reasons lately.

I don't know what benchmarks would be representative of actual elisp 
usage, but on my build machine both make bootstrap and make check are 
consistently ~8% slower on correct-warning-pos vs master:

make -j1 bootstrap: 649s vs 596s
make -j4 bootstrap: 257s vs 238s
make -j8 bootstrap: 198s vs 183s

make -j1 check: 178s vs 162s
make -j4 check: 44s vs 40s
make -j8 check: 26s vs 24s