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

On 10/14/2015 09:37 AM, Pierre-Marie de Rodat wrote:
> And to me as well: thank you Ulrich for this crystal clear explanation.
> :-) I will give it a try next week, then.

Quick update: I started to dig into this. I still have a hard time 
wrapping the current implementation in my mind[1] and thinking about 
what we should do exactly:

   * Have different types for expressions and location lists (hence 
potentially renaming existing code): looks like a big commit!

   * Introduce another entry point to evaluate dynamic properties as 
expressions. Looks like a small change but a weaker design: how to 
evaluate depends a property depends on the property, not the evaluation 
context, so it would be great to keep types distinct.

I cannot make any commitment on a schedule to implement this, though.


[1] Especially considering that dynamic properties handle only locations 
that resolve to an inferior address. Location resolution for variables 
don’t rely on this mechanism, which is some kind of inconsistency. On 
the other hand, dynamic properties are DWARF-specific…

-- 
Pierre-Marie de Rodat