On Mon, 26 Jun 2017, Segher Boessenkool wrote: > Hi! > > I'd like to backport the following patches to 7, 6, and where > applicable 5 (some are in 7 already). > > > https://gcc.gnu.org/ml/gcc-patches/2017-05/msg02107.html > Fix expand_builtin_atomic_fetch_op for pre-op (PR80902) > > https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01404.html > Fix comparison of decimal float zeroes (PR80692) > > https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00819.html > IRA: Don't create new regs for debug insns (PR80429) > > https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01050.html > lra: A multiple_sets is not a simple_move_p (PR73650)
The above look ok. > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg01853.html > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg01923.html > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg02048.html > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg02606.html > bb-reorder: Improve compgotos pass (PR71785) It's not clear this fixes a regression and as it is a missed-optimization I'd not backport it at this point in time (I understand it's in GCC 7 already). > https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00003.html > simplify-rtx: Fix compare of comparisons (PR60818) Ok. Thanks, Richard. > > Are those okay to backport? > > > And, rs6000 patches: > > https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00567.html > rs6000: Don't add an immediate to r0 (PR80966) > > https://gcc.gnu.org/ml/gcc-patches/2017-05/msg02408.html > rs6000: Don't write "nor" as (not (ior () ())) (PR80618) > > https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00568.html > rs6000: Enforce quad_address_p in TImode atomic_load/store (PR80382) > > https://gcc.gnu.org/ml/gcc-patches/2017-01/msg01543.html > rs6000: Small varargs for BE SVR4 (PR61729, PR77850) > > > Segher > > -- Richard Biener <rguent...@suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
