Google Git
Sign in
llvm / llvm-project / b36a446c3a897e667532611c2d508dbdb38eb52f
commitb36a446c3a897e667532611c2d508dbdb38eb52f[log] [tgz]
authorSterling-Augustine <saugustine@google.com>Mon Sep 08 14:20:55 2025 -0700
committerGitHub <noreply@github.com>Mon Sep 08 14:20:55 2025 -0700
tree8d9c94e6495caa3dbabe3478304accff8eb181a3
parent7f70bdde33e44689646fa6900be2c55df9d3176f [diff]
Parse CFI instructions to create SFrame FREs (#155496)

This PR parses CFI instructions to generate FREs. 

Unfortunately, actually emitting the FREs into the object file is
somewhat involved and would make this PR quite a bit harder to review.
And the dumper itself properly errors if the FRE count is included in
the header or FDEs, but they are not actually emitted. So actually
testing that the proper FREs are generated will have to wait for a
subsequent PR.

For now, just check for common issues with CFI that sframe doesn't
support, and that proper error handling is done.
3 files changed
tree: 8d9c94e6495caa3dbabe3478304accff8eb181a3
  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.