Re: dynamic array's upper bound evaluated as address for AVR target

> I think the current GDB "dynamic property" mechanism was probably intended
> to capture what DWARF section 2.19 specifies, but due to its simultaneous
> use for DW_AT_data_location and DW_AT_static_link, things got confused.
> 
> It would probably be best to clearly separate this out into two separate
> mechanisms, one that precisely implements dynamic properties as defined
> in section 2.19, and one that implements location descriptions.  (Note
> that those mechanism should ideally then be used for some of the *other*
> places where the DWARF standard also allows either a dynamic property or
> a location description, but GDB doesn't accept them yet.)
> 
> This would then have the side effect that we could distinguish return
> types: location descriptions always return an address, but section 2.19
> dynamic attributes always return an integer.

Sounds correct to me.

-- 
Joel