forked from OSchip/llvm-project
632ebc4ab4
This untangles the MCContext and the MCObjectFileInfo. There is a circular dependency between MCContext and MCObjectFileInfo. Currently this dependency also exists during construction: You can't contruct a MOFI without a MCContext without constructing the MCContext with a dummy version of that MOFI first. This removes this dependency during construction. In a perfect world, MCObjectFileInfo wouldn't depend on MCContext at all, but only be stored in the MCContext, like other MC information. This is future work. This also shifts/adds more information to the MCContext making it more available to the different targets. Namely: - TargetTriple - ObjectFileType - SubtargetInfo Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D101462 |
||
|---|---|---|
| .. | ||
| amdgpu-arch | ||
| apinotes-test | ||
| arcmt-test | ||
| c-arcmt-test | ||
| c-index-test | ||
| clang-check | ||
| clang-diff | ||
| clang-extdef-mapping | ||
| clang-format | ||
| clang-format-vs | ||
| clang-fuzzer | ||
| clang-import-test | ||
| clang-offload-bundler | ||
| clang-offload-wrapper | ||
| clang-refactor | ||
| clang-rename | ||
| clang-scan-deps | ||
| clang-shlib | ||
| diag-build | ||
| diagtool | ||
| driver | ||
| libclang | ||
| scan-build | ||
| scan-build-py | ||
| scan-view | ||
| CMakeLists.txt | ||