Yee Cheng Chin aff7a2f6dd Use -O3 and link-time-optimization for published builds ...

From testing and benchmarking, it appears that both result in a
measurable improvement in performance, wtih some benchmarks showing 10%
faster (when opening a large 400 MB binary file and
searching-and-replacing within it). Use them when building a published
build. Don't do it for legacy builds as I encountered some issues with
it failing tests when testing for recursion limit and I suspect it's due
to stack size issues. Since legacy builds are mostly kept for
compatibility reasons, no need to optimize it for now.

2023-10-16 03:04:33 -07:00

..

appveyor.bat

patch 9.0.1206: testing with Python on AppVeyor does not work properly

2023-01-16 13:01:28 +00:00

config.mk.clang-12.sed

patch 9.0.1960: Make CI checks more strict

2023-09-30 12:32:37 +02:00

config.mk.clang.sed

Merge remote-tracking branch 'vim/master'

2022-01-03 14:33:39 +09:00

config.mk.gcc.sed

patch 8.2.0828: Travis: regexp patttern doesn't work everywhere

2020-05-26 20:09:11 +02:00

config.mk.optimized.sed

Use -O3 and link-time-optimization for published builds

2023-10-16 03:04:33 -07:00

config.mk.sed

patch 9.0.1960: Make CI checks more strict

2023-09-30 12:32:37 +02:00

if_ver-1.vim

patch 8.2.2733: detecting Lua version is not reliable

2021-04-07 20:11:12 +02:00

if_ver-2.vim

patch 8.2.0140: CI does not test building doc tags

2020-01-21 22:13:42 +01:00

if_ver-cmd.vim

patch 8.2.0140: CI does not test building doc tags

2020-01-21 22:13:42 +01:00

setup-xvfb.sh

patch 8.2.2150: Github actions CI isn't used for all available platforms

2020-12-17 20:27:26 +01:00