forked from OSchip/llvm-project
df054d3d22
Essentially, as a base class constructor does not construct virtual bases, such a constructor for an abstract class does not need the corresponding base class construction to be valid, and likewise for destructors. This creates an awkward situation: clang will sometimes generate references to the complete object and deleting destructors for an abstract class (it puts them in the construction vtable for a derived class). But we can't generate a "correct" version of these because we can't generate references to base class constructors any more (if they're template specializations, say, we might not have instantiated them and can't assume any other TU will emit a copy). Fortunately, we don't need to, since no correct program can ever invoke them, so instead emit symbols that just trap. We should stop emitting references to these symbols, but still need to emit definitions for compatibility. llvm-svn: 296275 |
||
|---|---|---|
| .. | ||
| basic | ||
| class | ||
| class.access | ||
| class.derived | ||
| concepts-ts | ||
| conv | ||
| cpp/cpp.predefined | ||
| dcl.dcl | ||
| dcl.decl | ||
| drs | ||
| except | ||
| expr | ||
| lex | ||
| over | ||
| special | ||
| stmt.stmt | ||
| temp | ||