Mercurial > vim
changeset 34021:46ebf4ffad49 v9.0.2186
patch 9.0.2186: LTCG compile error ARM64 for write_chars
Commit: https://github.com/vim/vim/commit/38bea30f53da8e4a8847407404597b255b20334e
Author: Saleem Abdulrasool <compnerd@compnerd.org>
Date: Wed Dec 27 18:57:12 2023 +0100
patch 9.0.2186: LTCG compile error ARM64 for write_chars
Problem: LTCG compile error on Win/ARM64 for `write_chars()`
Solution: Explicitly initialise the storage to use data rather than BSS
(Saleem Abdulrasool)
win32: add a workaround for a LTCG issue on Windows ARM64
It appears that the implicit initialisation which would push `g_coords`
into BSS causes an aliasing issue with LTCG on ARM64. By explicitly
initialising the value, we use usual data storage but prevent the
aliasing. This allows the console version of VIM to run on Windows
ARM64 again.
fixes: #13453
closes: #13775
Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org>
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Wed, 27 Dec 2023 19:15:03 +0100 |
| parents | fb167ca472fe |
| children | dc7094ebb231 |
| files | src/os_win32.c src/version.c |
| diffstat | 2 files changed, 6 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/src/os_win32.c +++ b/src/os_win32.c @@ -156,7 +156,10 @@ static HANDLE g_hConOut = INVALID_HANDLE // Win32 Screen buffer,coordinate,console I/O information static SMALL_RECT g_srScrollRegion; -static COORD g_coord; // 0-based, but external coords are 1-based +// This is explicitly initialised to work around a LTCG issue on Windows ARM64 +// (at least of 19.39.33321). This pushes this into the `.data` rather than +// `.bss` which corrects code generation in `write_chars` (#13453). +static COORD g_coord = {0, 0}; // 0-based, but external coords are 1-based // The attribute of the screen when the editor was started static WORD g_attrDefault = 7; // lightgray text on black background