| commit | 95657630bda3e73c19d190e25fd9d92b07fc3455 | [log] [tgz] |
|---|---|---|
| author | Daniel Paoliello <danpao@microsoft.com> | Fri Aug 29 09:00:01 2025 -0700 |
| committer | GitHub <noreply@github.com> | Fri Aug 29 09:00:01 2025 -0700 |
| tree | ea9d1305eda8f28a3615e8375743be6dee444653 | |
| parent | 4159fd819a89cb18e03a91576372ae257ee5fbc7 [diff] |
[win][x64] Various fixes for unwind v2 (#154834) * `SetFrame` does not count as a stack allocation. * `mov` in the epilog undoes `SetFrame` (but is not required), it does not deallocate a stack allocation. * `mov` in the epilog MUST be before any stack deallocation or register popping. * Remove assert for having a prolog without any epilogs (this is possible for `noreturn` functions, for instance). * Improve the errors in `MC` to include the problematic function name.
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.