Skip to content

Commit 392a65e

Browse files
committed
fixup! max_tree_depth: lower it for clangarm64 on Windows
I have upstreamed this already as 436a422 (max_tree_depth: lower it for clangarm64 on Windows, 2025-04-23). This reverts commit 1d52d30 (max_tree_depth: lower it for clangarm64 on Windows, 2025-04-15). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
1 parent 2912d8e commit 392a65e

1 file changed

Lines changed: 0 additions & 12 deletions

File tree

environment.c

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -101,21 +101,9 @@ int max_allowed_tree_depth =
101101
* tree depth; This value seems to be low enough.
102102
*/
103103
1280;
104-
#else
105-
#if defined(GIT_WINDOWS_NATIVE) && defined(__clang__) && defined(__aarch64__)
106-
/*
107-
* Similar to Visual C, it seems that on Windows/ARM64 the clang-based
108-
* builds have a smaller stack space available. When running out of
109-
* that stack space, a `STATUS_STACK_OVERFLOW` is produced. When the
110-
* Git command was run from an MSYS2 Bash, this unfortunately results
111-
* in an exit code 127. Let's prevent that by lowering the maximal
112-
* tree depth; This value seems to be low enough.
113-
*/
114-
1280;
115104
#else
116105
2048;
117106
#endif
118-
#endif
119107

120108
#ifndef PROTECT_HFS_DEFAULT
121109
#define PROTECT_HFS_DEFAULT 0

0 commit comments

Comments
 (0)