On 12/03/13 11:40, Bernd Edlinger wrote:
To me it does not feel like a hack at all, if the expansion needs to know in
what
context the result will be used, if it is in an LHS or in a RHS or if the
address of
the memory is needed.
Expansion needs some context and it's currently passed into expand_expr
via a variety of methods. Most are documented at the start of
expand_expr_real. It's unclean, but that doesn't mean we should make it
worse. Adding more context is something we should think long and hard
about.
Eric's comment that we have a non-BLKmode object with a variable size I
think is critical. I'm pretty sure that's not a well-defined object.
Given a variable sized object that is not BLKmode, how can we reliably
get its size (you can't, that's part of the reason why BLKmode exists)
I'd pull on that thread.
To make that perfectly clear, I just want to help.
Understood and its greatly appreciated.
And even if I commit something, it can be reverted anytime, when we have
something better.
We try to get it right the first time :-) Reverting bits is undesirable
and virtually impossible if it gets out into a release.
jeff
