This patch implements the DWARFv5 feature where a
DW_AT_defaulted is attached to DW_TAG_subprograms
which are explicitly defaulted in C++, i.e., member
functions such as the following:
class C { C() = default; ~C() = default; };
We add two new spFlags, one for each possible value of
DW_AT_defaulted (see table in section 5.7.8 of DWARFv5
specification).
Is there any particular benefit to providing this fidelity (the difference between defaulted in class and defaulted out of class)? (sorry, this might split the "motivation" design discussion between this patch and the clang frontend patch) and/or should we use an enum here (it wouldn't save us a bit, but would avoid create a representation that could have both DefaultedInClass and DefaultedOutOfClass true at the same time, which isn't necessary/useful)