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 r11-9244] Daily bump. Date: Wed, 17 Nov 2021 00:18:47 +0000 (GMT) [thread overview] Message-ID: <20211117001847.45C4F3858410@sourceware.org> (raw) https://gcc.gnu.org/g:69c65785e47bbec5aa28af6b6e393e997bdc66f3 commit r11-9244-g69c65785e47bbec5aa28af6b6e393e997bdc66f3 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Wed Nov 17 00:18:15 2021 +0000 Daily bump. Diff: --- gcc/ChangeLog | 13 +++++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 25 +++++++++++++++++++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ 4 files changed, 47 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 9a2610f8dd0..b01ab5b6c7e 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,16 @@ +2021-11-16 Philipp Tomsich <philipp.tomsich@vrull.eu> + + Backported from master: + 2021-11-03 Philipp Tomsich <philipp.tomsich@vrull.eu> + + * config/aarch64/aarch64-cores.def (AARCH64_CORE): New Ampere-1 + core. + * config/aarch64/aarch64-tune.md: Regenerate. + * config/aarch64/aarch64-cost-tables.h: Add extra costs for + Ampere-1. + * config/aarch64/aarch64.c: Add tuning structures for Ampere-1. + * doc/invoke.texi: Add documentation for Ampere-1 core. + 2021-11-15 Kewen Lin <linkw@linux.ibm.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 7090fb4b3b1..530e4a51b6a 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20211116 +20211117 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 47db52f0052..bfd505e60ae 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,28 @@ +2021-11-16 Mikael Morin <mikael@gcc.gnu.org> + + Backported from master: + 2021-11-12 Mikael Morin <mikael@gcc.gnu.org> + + PR fortran/97896 + * intrinsic.c (add_sym_4ind): Remove. + (add_functions): Use add_sym4 instead of add_sym4ind. + Don’t special case the index intrinsic. + * iresolve.c (gfc_resolve_index_func): Use the individual arguments + directly instead of the full argument list. + * intrinsic.h (gfc_resolve_index_func): Update the declaration + accordingly. + * trans-decl.c (gfc_get_extern_function_decl): Don’t modify the + list of arguments in the case of the index intrinsic. + * trans-array.h (gfc_get_intrinsic_for_expr, + gfc_get_proc_ifc_for_expr): New. + * trans-array.c (gfc_get_intrinsic_for_expr, + arg_evaluated_for_scalarization): New. + (gfc_walk_elemental_function_args): Add intrinsic procedure + as argument. Count arguments. Check arg_evaluated_for_scalarization. + * trans-intrinsic.c (gfc_walk_intrinsic_function): Update call. + * trans-stmt.c (get_intrinsic_for_code): New. + (gfc_trans_call): Update call. + 2021-11-11 Harald Anlauf <anlauf@gmx.de> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index ea33050376c..778148bc6ac 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2021-11-16 Mikael Morin <mikael@gcc.gnu.org> + + Backported from master: + 2021-11-12 Mikael Morin <mikael@gcc.gnu.org> + + PR fortran/97896 + * gfortran.dg/index_5.f90: New. + 2021-11-10 Richard Biener <rguenther@suse.de> Backported from master:
reply other threads:[~2021-11-17 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=20211117001847.45C4F3858410@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).