diff options
| author | Aaron Puchert <aaron.puchert@sap.com> | 2021-11-12 21:09:40 +0100 |
|---|---|---|
| committer | Aaron Puchert <aaron.puchert@sap.com> | 2021-11-12 21:11:11 +0100 |
| commit | 3010883fc296619def051e0a2f97d40fb15960d7 (patch) | |
| tree | 5e373ca249d5e2b6415d6f8d0ee79ea6c3fe231c /llvm/lib/Transforms/Utils/LoopUnrollRuntime.cpp | |
| parent | 4e7df1ef7b679953c1501177539166876c4cbda4 (diff) | |
| download | llvm-3010883fc296619def051e0a2f97d40fb15960d7.zip llvm-3010883fc296619def051e0a2f97d40fb15960d7.tar.gz llvm-3010883fc296619def051e0a2f97d40fb15960d7.tar.bz2 | |
Comment AST: Recognize function-like objects via return type (NFC)
Instead of pretending that function pointer type aliases or variables
are functions, and thereby losing the information that they are type
aliases or variables, respectively, we use the existence of a return
type in the DeclInfo to signify a "function-like" object.
That seems pretty natural, since it's also the return type (or parameter
list) from the DeclInfo that we compare the documentation with.
Addresses a concern voiced in D111264#3115104.
Reviewed By: gribozavr2
Differential Revision: https://reviews.llvm.org/D113691
Diffstat (limited to 'llvm/lib/Transforms/Utils/LoopUnrollRuntime.cpp')
0 files changed, 0 insertions, 0 deletions