diff options
author | Serge Pavlov <sepavloff@gmail.com> | 2017-06-14 10:07:02 +0000 |
---|---|---|
committer | Serge Pavlov <sepavloff@gmail.com> | 2017-06-14 10:07:02 +0000 |
commit | c73c81be5c8fdb8d27acb87623c252b665ac3b42 (patch) | |
tree | aaa2b2909f138b50ba7b9d5adc2601eedc952d22 /lldb/packages/Python/lldbsuite | |
parent | 0c29ef1b8055a504ff0ca6a610eb47f2637235e0 (diff) | |
download | bcm5719-llvm-c73c81be5c8fdb8d27acb87623c252b665ac3b42.tar.gz bcm5719-llvm-c73c81be5c8fdb8d27acb87623c252b665ac3b42.zip |
Function with unparsed body is a definition
While a function body is being parsed, the function declaration is not considered
as a definition because it does not have a body yet. In some cases it leads to
incorrect interpretation, the case is presented in
https://bugs.llvm.org/show_bug.cgi?id=14785:
```
template<typename T> struct Somewhat {
void internal() const {}
friend void operator+(int const &, Somewhat<T> const &) {}
};
void operator+(int const &, Somewhat<char> const &x) { x.internal(); }
```
When statement `x.internal()` in the body of global `operator+` is parsed, the type
of `x` must be completed, so the instantiation of `Somewhat<char>` is started. It
instantiates the declaration of `operator+` defined inline, and makes a check for
redefinition. The check does not detect another definition because the declaration
of `operator+` is still not defining as does not have a body yet.
To solves this problem the function `isThisDeclarationADefinition` considers
a function declaration as a definition if it has flag `WillHaveBody` set.
This change fixes PR14785.
Differential Revision: https://reviews.llvm.org/D30375
llvm-svn: 305379
Diffstat (limited to 'lldb/packages/Python/lldbsuite')
0 files changed, 0 insertions, 0 deletions