This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Proposal for merging scalar-storage-order branch into mainline

On Tue, Jun 9, 2015 at 12:39 PM, Eric Botcazou <> wrote:
>> What's the reason to not expose the byte swapping operations earlier, like
>> on GIMPLE?  (or even on GENERIC?)
> That would be too heavy, every load and store in GENERIC/GIMPLE would have an
> associated byte swapping operation, although you don't know if they will be
> needed in the end.  For example, if the structure is scalarized, they are not.

Yes, but I'd expect them to be optimized away (well, hopefully).
Anwyay, and I thought
use of the feature would be rare so that "every load and store" is
still very few?

I suppose doing the lowering somewhen during the GIMPLE optimization pipeline
would still be possible to address missed-optimization concerns.

>> What frontends are affected?
> The branch contains a working implementation for the C and Ada front-ends, and
> the beginning of an implementation for the C++ front-end.

Ok, I see.


> --
> Eric Botcazou

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]