This is a continuation of the patch series I started on Wednesday this time posted under a covering message. Parts 1-5 were:
[1/n] https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01634.html [2/n] https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01637.html [3/n] https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01638.html [4/n] https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01639.html [5/n] https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01641.html Some parts of the series will conflict with Andre's patches, so I'll hold off applying anything that gets approved until those patches have gone in. The conflicts should only be minor though, and won't change the approach, so I thought it was worth posting for comments now anyway. I tested each patch individually on aarch64-linux-gnu and the series as a whole on x86_64-linux-gnu. I also tried building at least one target per CPU directory and spot-checked that they were behaving sensibly after the patch. Thanks, Richard
