[llvm-dev] Aggregate load/stores

[Joerg Sonnenberger via llvm-dev]

On Tue, Aug 18, 2015 at 03:23:20PM +0200, Jonas Maebe via llvm-dev wrote:
> 
> deadal nix via llvm-dev wrote on Mon, 17 Aug 2015:
> 
> >OK, what about that plan :
> >
> >Slice the aggregate into a serie of valid loads/stores for non atomic ones.
> >Use big scalar for atomic/volatile ones.
> >Try to generate memcpy or memmove when possible ?
> 
> Are memcpy/memmove guaranteed to be handled inline, i.e., without a
> call to libc? Or are there plans to do this in the context of the
> (afaik) long term goal of enabling llvm to (optionally) generate
> freestanding code? If not, generating memcpy/memmove seems like a
> bad idea, as it would make that goal harder to achieve.

Freestanding code is still documented to require memset and a few other
things.

Joerg