The spec does say they occur in the same order, which strongly implies that
there is a DW_TAG_call_site_parameter for each actual parameter. Although, now
that I say that, I have a memory of some discussion where a parameter entry
might be omitted entirely. I don’t remember the details, but Jaku
In that case I shall create appropriate issues for the mentioned compilers in
order to discuss the matter with them.
I think I have found another issue with clang. In some cases it does not
generate middle parameters: namely, it skipped the 2nd one yet included the 3rd
one.
It believe it does n
I believe this is an issue with the implementations, although it is a bit odd
that both gcc and clang behave the same way. There should be a
DW_TAG_call_site_parameter for each parameter. DW_AT_location should describe
the stack slot where the parameter is passed. It should not be a problem for
Consider a type that is a subrange of an integral base type, with an
explicitly specified bit size smaller than the bit width of a storage
unit.
When used for a standalone variable, its byte size is the same as that
of the base type, i.e., the type is padded to a whole unit.
However, when used
