On 10/06/2015 12:57 PM, Eric Botcazou wrote:
this is a repost of the diff of the scalar-storage-order branch vs mainline.
It contains the fixes suggested by Joseph for the C front-end and the doc,
fixes for the handling of complex types, the new pragma scalar_storage_order
and associated -fsso-struct switch for the C family of languages, and the
adjustment for vector types suggested by Ramana, plus assorted fixes:
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg00024.html
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg00138.html
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01500.html
See https://gcc.gnu.org/ml/gcc/2015-06/msg00126.html for the proposal.
I have split the diff into 6 pieces, which are interdependent and thus cannot
be applied independently: 3 for the Ada, C and C++ front-ends, 1 for the bulk
of the implementation, 1 for the rest and 1 for the testsuite.
It has been bootstrapped/regtested on x86_64-linux and powerpc-linux.
My main question about this series is - how generally useful do you
expect it to be? I know of some different projects that would like
bi-endian capability, but it looks like this series implements something
that is a little too limited to be of use in these cases. It looks like
it comes with a nontrivial maintenance cost.
Bernd
