| commit | 77a8e95f6cc7395a1fd5c345479181d9ec692769 | [log] [tgz] |
|---|---|---|
| author | Matheus Izvekov <mizvekov@gmail.com> | Sat Aug 10 23:43:27 2024 -0300 |
| committer | Matheus Izvekov <mizvekov@gmail.com> | Mon Sep 09 21:10:21 2024 -0300 |
| tree | 074f7dc6832017abc5740233b2062844eac9dbde | |
| parent | f2b71491d11355c0df0c92ef7cce7d610c894660 [diff] |
[clang] WIP: Improved Context Declaration tracking This patch aims to improve how parenting relationships are represented in the AST. Currently regular declarations can only be children of special AST nodes which inherit from DeclContext, except for a few special cases which are required by itanium mangling. Having this parenting relationship well described helps in tracking which entities are dependent, and an improvement here would allow us to drop a lot of workarounds and to get some difficult cases right. This patch extends the ContextDecl tracking which currently is used for mangling, in order to cover almost needed cases. Template type aliases represent a specially difficult case which is addressed by this patch. They can be contexts for other declarations, but besides not being DeclContexts, they also lack a declaration which represents their specialization. This patch addresses the type alias context problem by storing the specialization arguments along with the ContextDecl for entities declared in their context. TODO: * Move away from using ExpressionEvaluationContexts, and use the same stack used for tracking the CurContext. Remove the separate ContextDecl field, and have that functionally built in to the base Decl class, so that we don't separatelly treack both a parent Decl and a parent DeclContext. * A function type has ParmVarDecls, and these can appear inside aliases and template type aliases in particular, so a ParmvarDecl needs a ContextDecl too.
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.