[NFC] Re-enable MSVC C4611 diagnostic (#182100) From MSDN: https://learn.microsoft.com/en-us/cpp/error-messages/compiler-warnings/compiler-warning-level-4-c4611?view=msvc-170 I do not believe this diagnostic happens in our code base any longer. This diagnostic was disabled in 5c73e1f85c5d37a5b037c70f3c112eec5646acb3 and the review for it (https://reviews.llvm.org/D8572) says there were two instances of the diagnostic as of 2015. But because this is about interaction between `setjmp` and C++ object destruction, I don't think we need to disable this diagnostic across the entire monorepo; we can silence it for the project using setjmp if it still exists. I enabled the diagnostic locally and my build was warning-free but I'd like to see how pre- (and post-)commit CI do with this one.
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.