Google Git
Sign in
llvm / llvm-project / b4fb9aa0f7edb009e1bb44240e75a9141a064b8c
commitb4fb9aa0f7edb009e1bb44240e75a9141a064b8c[log] [tgz]
authorBalázs Kéri <balazs.keri@ericsson.com>Fri Aug 29 09:45:39 2025 +0200
committerGitHub <noreply@github.com>Fri Aug 29 09:45:39 2025 +0200
tree330d493d4e4a72b9540d465953ca2a82c2577ef1
parenta805dfbc9f8fd7970b1376b1b9362ce1320fc04c [diff]
[clang] Fix of a crash 'Cannot get layout of forward declarations' during CTU static analysis (#155375)

When a type is imported with `ASTImporter`, the "original declaration"
of the type is imported. In some cases this is not the definition (of
the class). Before the fix the definition was only imported if there was
an other reference to it in the AST to import. This is not always the
case (like in the added test case), if not the definition was missing in
the "To" AST which can cause the assertion later.
2 files changed
tree: 330d493d4e4a72b9540d465953ca2a82c2577ef1
  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.