public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [OG10] Merge GCC 10 into branch; two cherry picks
Date: Tue, 15 Sep 2020 10:47:43 +0200	[thread overview]
Message-ID: <49dd2f72-f334-eac1-90c6-f7fbef00b52f@codesourcery.com> (raw)

OG10 = devel/omp/gcc-10

Committed backport plus two cherry picks:

a93cc852103 [PATCH] OpenMP/Fortran: Fix (re)mapping of allocatable/pointer arrays [PR96668]
e524656359b Merge remote-tracking branch 'origin/releases/gcc-10' into devel/omp/gcc-10
        f73772df64c Daily bump.
        0ea1b39e8e5 doc: fix spelling of -fprofile-reproducibility
        1c34981a9ba bpf: use the expected instruction for NOPs
        1dbb919d086 tree-optimization/96522 - transfer of flow-sensitive info in copy_ref_info
        e93428a8b05 tree-optimization/97043 - fix latent wrong-code with SLP vectorization
        7ad48f0a6b4 i386: Fix array index in expander
fafbe5379f9 [libgomp, nvptx] Add __sync_compare_and_swap_16
        1bcbc4da6ae Daily bump.
        23ee7de0be0 Improve costs for DImode shifts of interger constants.
        1660e831614 Daily bump.
        08a0f33a1b0 Add new shrpsi and shrpdi instruction variants to gcc/config/pa/pa.md.
        32ca9bb4201 Daily bump.

-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter

                 reply	other threads:[~2020-09-15  8:47 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=49dd2f72-f334-eac1-90c6-f7fbef00b52f@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@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: link
Be 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).