[foreign] RFR 8218153: Read/Write of Value layout should honor declared endianness

[John Rose]

On Feb 7, 2019, at 1:19 AM, Maurizio Cimadamore <maurizio.cimadamore at oracle.com> wrote:
> 
> If the replacement happens inside a function, the resolution machinery will take care of 'stripping' endianness of the replaced layout.
> 
> This is doable of course, but it's more complexity (both in impl and in terms of user model) - are we ok with it?

I'm OK with stripping endian-ness in specific situations
where the layout is being used in a container (i.e., a register)
rather than in memory.

One way to think about this is that such a layout is being
used to specify a container, not memory.  Maybe there's
some rule here to tease out for deriving a container from
a layout?