[CIR] Implement Namespace/global TLS CIR CodeGen (#196332)

Unlike local TLS, global TLS functions need to be initialized upon their
first use in a thread.

First, all attempts to 'get' said TLS global are replaced with calls to
a 'wrapper' function, which calls an 'init' alias function, then returns
the global. While classic codegen manages to omit this in simple cases
sometimes, this CIR implementation doesn't attempt to do such constant
folding/inlining. The call to the 'init' is omitted if there is no
ctor/dtor setup required, so sometimes the wrapper is just a 'no-op'
(intentionally!).

There are also two types of 'global' TLS functions: unordered, and
ordered. Unordered are typically variable templates, and their 'init'
function initializes JUST them. The rest are ordered, which requires all
ordered initializations to happen as soon as any happen.

The Wrapper:
If necessary (omitted in a few places), calls the 'init' alias, then
returns the global.

Global Init Function (__tls_init):
For ordered global TLS, a use of 1 TLS is required to initialize ALL of
them. This function checks the global guard (__tls_guard), and calls the
individual 'init' functions for each global(__cxx_global_var_init).
Unordered ones do not get entered here.

Individual init Functions (__cxx_global_var_init): Like the rest of our
globals, these emit a __cxx_global_var_init function. However, they are
not added to the global constructors list. These are identically emitted
with one exception: Unordered Global TLS variables wrap said init in a
guard check (ordered have their's guarded by __tls_guard in __tls_init).

Init Alias:
This alias is called by the wrapper function to make sure said variable
is initialized before use. IN the case of ordered globals, this is an
alias to __tls_init. IN the case of unordered globals, this goes
directly to the __cxx_global_var_init for that variable.

This patch implements the codegen part of the above by introducing a set
of 3 strings on a GlobalOp in an attribute. if present, this will cause
the above global tls behavior (with the next patch). At the moment, this
only generates the attribute, and the lowering-prepare patches will come
in future patches.
12 files changed
tree: abae003be06ccb7f8660fde56d1ef3c66189ebdd
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

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.

Getting the Source Code and Building LLVM

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.

Getting in touch

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.