public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-171] Daily bump. Date: Sun, 23 Apr 2023 00:18:04 +0000 (GMT) [thread overview] Message-ID: <20230423001804.A61293858C50@sourceware.org> (raw) https://gcc.gnu.org/g:6ab856aa49bef7c04efa6144a5048e129b3a058b commit r14-171-g6ab856aa49bef7c04efa6144a5048e129b3a058b Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sun Apr 23 00:17:23 2023 +0000 Daily bump. Diff: --- gcc/ChangeLog | 34 +++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 7 ++++++ gcc/testsuite/ChangeLog | 58 +++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 100 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index daf75783779..d8e0e5aa41c 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,37 @@ +2023-04-22 Andrew Pinski <apinski@marvell.com> + + * tree-ssa-phiopt.cc (tree_ssa_phiopt_worker): + Change the code around slightly to move diamond + handling for do_store_elim/do_hoist_loads out of + the big if/else. + +2023-04-22 Andrew Pinski <apinski@marvell.com> + + * tree-ssa-phiopt.cc (tree_ssa_phiopt_worker): + Remove check on empty_block_p. + +2023-04-22 Jakub Jelinek <jakub@redhat.com> + + PR bootstrap/109589 + * system.h (class auto_mpz): Workaround PR62101 bug in GCC 4.8 and 4.9. + * realmpfr.h (class auto_mpfr): Likewise. + +2023-04-22 Jakub Jelinek <jakub@redhat.com> + + PR tree-optimization/109583 + * match.pd (fneg/fadd simplify): Don't call related_vector_mode + if vec_mode is not VECTOR_MODE_P. + +2023-04-22 Jan Hubicka <hubicka@ucw.cz> + Ondrej Kubanek <kubanek0ondrej@gmail.com> + + * cfgloopmanip.h (adjust_loop_info_after_peeling): Declare. + * tree-ssa-loop-ch.cc (ch_base::copy_headers): Fix updating of + loop profile and bounds after header duplication. + * tree-ssa-loop-ivcanon.cc (adjust_loop_info_after_peeling): + Break out from try_peel_loop; fix handling of 0 iterations. + (try_peel_loop): Use adjust_loop_info_after_peeling. + 2023-04-21 Andrew MacLeod <amacleod@redhat.com> PR tree-optimization/109546 diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 255d261f77a..e372b3d6ca6 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230422 +20230423 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 4fa083acf3c..3db84b9edda 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,10 @@ +2023-04-22 Harald Anlauf <anlauf@gmx.de> + Steven G. Kargl <kargl@gcc.gnu.org> + + PR fortran/109500 + * interface.cc (gfc_compare_actual_formal): Reject allocatable + functions being used as actual argument for allocable dummy. + 2023-04-14 Harald Anlauf <anlauf@gmx.de> PR fortran/109511 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index dd0b91d07b9..028a8bc7af8 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,61 @@ +2023-04-22 Andrew Pinski <apinski@marvell.com> + + * gcc.dg/tree-ssa/phi-opt-5.c: Remvoe some xfail. + +2023-04-22 Roger Sayle <roger@nextmovesoftware.com> + + PR target/54816 + * gcc.target/avr/pr54816.c: Move to... + * gcc.target/avr/mmcu/pr54816.c: ... here. + +2023-04-22 Harald Anlauf <anlauf@gmx.de> + Steven G. Kargl <kargl@gcc.gnu.org> + + PR fortran/109500 + * gfortran.dg/allocatable_function_11.f90: New test. + +2023-04-22 Jakub Jelinek <jakub@redhat.com> + + PR testsuite/109572 + * gcc.dg/vect/pr109011-1.c: In scan-tree-dump-times regexps match also + vect prefix to make sure we only count vectorized calls. + * gcc.dg/vect/pr109011-2.c: Likewise. On powerpc* expect just count 3 + rather than 4. + * gcc.dg/vect/pr109011-3.c: In scan-tree-dump-times regexps match also + vect prefix to make sure we only count vectorized calls. + * gcc.dg/vect/pr109011-4.c: Likewise. On powerpc* expect just count 3 + rather than 4. + (foo): Add 2 further arithmetic ops to the loop to make it appear + worthwhile for vectorization heuristics on powerpc. + * gcc.dg/vect/pr109011-5.c: In scan-tree-dump-times regexps match also + vect prefix to make sure we only count vectorized calls. + (foo): Add 2 further arithmetic ops to the loop to make it appear + worthwhile for vectorization heuristics on powerpc. + +2023-04-22 Jeff Law <jlaw@ventanamicro> + + * gcc.target/rx/movsicc.c: Broken down into ... + * gcc.target/rx/movsicc-1.c: Here. + * gcc.target/rx/movsicc-2.c: Here. + * gcc.target/rx/movsicc-3.c: Here. xfail one test. + * gcc.target/rx/movsicc-4.c: Here. + * gcc.target/rx/movsicc-5.c: Here. + * gcc.target/rx/movsicc-6.c: Here. + * gcc.target/rx/movsicc-7.c: Here. + * gcc.target/rx/movsicc-8.c: Here. + +2023-04-22 Jakub Jelinek <jakub@redhat.com> + + PR tree-optimization/109583 + * gcc.dg/pr109583.c: New test. + +2023-04-22 Jan Hubicka <hubicka@ucw.cz> + Ondrej Kubanek <kubanek0ondrej@gmail.com> + + * gcc.dg/tree-ssa/peel1.c: Decrease number of peels by 1. + * gcc.dg/unroll-8.c: Decrease loop iteration estimate. + * gcc.dg/tree-prof/peel-2.c: New test. + 2023-04-21 Andrew MacLeod <amacleod@redhat.com> PR tree-optimization/109546
reply other threads:[~2023-04-23 0:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230423001804.A61293858C50@sourceware.org \ --to=gccadmin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).