public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Peter Bergner <bergner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/ibm/heads/gcc-10-branch)] ibm: Merge up to top of releases/gcc-10 Date: Tue, 15 Sep 2020 19:09:17 +0000 (GMT) [thread overview] Message-ID: <20200915190917.C84DB394504F@sourceware.org> (raw) https://gcc.gnu.org/g:ae2560c44144ff2716ea114c91205a914411df10 commit ae2560c44144ff2716ea114c91205a914411df10 Merge: 89146d29e7c 49b3d88e9dc Author: Peter Bergner <bergner@linux.ibm.com> Date: Tue Sep 15 12:35:12 2020 -0500 ibm: Merge up to top of releases/gcc-10 2020-09-15 Peter Bergner <bergner@linux.ibm.com> Merge up to releases/gcc-10 49b3d88e9dc9314814d416dcebc25ca028576c30 Diff: gcc/ChangeLog.ibm | 4 ++++ gcc/config/rs6000/rs6000-call.c | 4 ++-- gcc/testsuite/gcc.target/powerpc/pr96139-a.c | 32 ++++++++++++++++++++++++++++ gcc/testsuite/gcc.target/powerpc/pr96139-b.c | 32 ++++++++++++++++++++++++++++ gcc/testsuite/gcc.target/powerpc/pr96139-c.c | 26 ++++++++++++++++++++++ 5 files changed, 96 insertions(+), 2 deletions(-) diff --cc gcc/ChangeLog.ibm index e0bda75d7c4,00000000000..baff9a0772a mode 100644,000000..100644 --- a/gcc/ChangeLog.ibm +++ b/gcc/ChangeLog.ibm @@@ -1,31 -1,0 +1,35 @@@ ++2020-09-15 Peter Bergner <bergner@linux.ibm.com> ++ ++ Merge up to releases/gcc-10 49b3d88e9dc9314814d416dcebc25ca028576c30 ++ +2020-09-15 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 55cd12c65ffa1e7c0bb36fd398f178d5d15d660f + +2020-09-03 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 abd9341c2f1ae5f7aa73950cdaac58ef3a2f0190 + +2020-08-18 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 7f976034ec4997d2df5ede70c1312de3acd7b4c4 + +2020-07-30 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 809b4d226c7f5ded392a88ffafe8d652f911b473 + +2020-07-23 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 5497677b497b95a261089d19f5295cc80f99a2b6 + +2020-07-02 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 034e7f1d295140344f3849ebba1d352cad01da27 + +2020-07-02 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 41b504e91e5cd0fdce36b7306ce42dd592c401f2 + +2020-06-24 Peter Bergner <bergner@linux.ibm.com> + + Merge up to releases/gcc-10 8e25bae517450c001f5e84b7ab24f06bb1425df6.
next reply other threads:[~2020-09-15 19:09 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-15 19:09 Peter Bergner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-08-01 19:33 Peter Bergner 2023-03-06 22:37 Peter Bergner 2022-08-24 0:43 Peter Bergner 2022-03-29 22:32 Peter Bergner 2022-02-18 23:33 Peter Bergner 2022-01-15 7:09 Peter Bergner 2021-09-22 13:24 Peter Bergner 2021-06-18 19:47 Peter Bergner 2021-04-12 18:59 Peter Bergner 2021-03-17 21:09 Peter Bergner 2021-01-04 22:27 Peter Bergner 2020-09-24 19:02 Peter Bergner 2020-09-15 16:44 Peter Bergner 2020-09-03 16:41 Peter Bergner 2020-08-19 14:02 Peter Bergner 2020-07-30 16:58 Peter Bergner 2020-07-23 19:06 Peter Bergner 2020-07-03 3:00 Peter Bergner 2020-07-02 21:09 Peter Bergner 2020-06-25 0:35 Peter Bergner
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=20200915190917.C84DB394504F@sourceware.org \ --to=bergner@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).