forked from OSchip/llvm-project
bcad53e131
When generic resolution finds its specific procedure in a module, and that specific procedure is not use-associated into the local scope (perhaps because it was PRIVATE, perhaps because the generic was use-associated with ONLY:), we create a new use-association with a renaming. The name constructed for this renaming needs to be additionally qualified with the module name of the specific procedure in order to avoid clashing with another specific of the same name that may have previously been use-associated in the same way from a distinct module. Differential Revision: https://reviews.llvm.org/D127790 |
||
|---|---|---|
| .. | ||
| Driver | ||
| Evaluate | ||
| Examples | ||
| Fir | ||
| Frontend | ||
| Lower | ||
| NonGtestUnit | ||
| Parser | ||
| Preprocessing | ||
| Runtime | ||
| Semantics | ||
| Unit | ||
| CMakeLists.txt | ||
| lit.cfg.py | ||
| lit.site.cfg.py.in | ||