Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[lli] Make sure the exported __chkstk functions are included when exp…
…orting them The trick we use (since cbc2a06) for exporting the __chkstk function (with various per-arch names) that is defined in a different object file, relies on the function already being linked in (by some function referencing it). This function does end up referenced if there's a function that allocates more than 4 KB on the stack. In most cases, it's referenced somewhere, but in the case of builds with LLVM_LINK_LLVM_DYLIB enabled (so most of the code resides in a separate libLLVM-<ver>.dll) the only code in lli.exe is the lli tool specific code and the mingw-w64 crt startup code. In the case of GCC based MinGW i386 builds with LLVM_LINK_LLVM_DYLIB, nothing else references it though. Manually add a reference to the function to make sure it is linked in (from libgcc or compiler-rt builtins) so that it can be exported. This fixes one build issue encountered in msys2/MINGW-packages#18002. Differential Revision: https://reviews.llvm.org/D159085 (cherry picked from commit 4bba12f)
- Loading branch information