On Thu, Aug 17, 2017 at 3:14 PM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > > I agree it's confusing, and yes I would like a better name. > OTOH 'registrable' is not exactly the conveyed meaning. > 'register' is a concept that pertains to the backend, that > is machine specific, a pseudo may need several registers > and a register can hold several pseudos, ... Sure, I saw your new name some thing like promote-able. That is good. > > Here what we really want to select is something along: > 'it's interesting to see it as a flow of value' vs. > 'it's better to see it as a change in state'. > And yes, very often that just correspond to registers. > > Note: it's not even 'what can be put in a pseudo(-register)' > were selecting here. It's OK to have pseudos for > 'non-simple' values, They will just be transient and we > won't be interested in their 'flow'. We need to be very careful about composite type pointer alias. Any pointer alias to the member of the struct need to take into account as well. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
