public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-11] (10 commits) Merge remote-tracking branch 'origin/releases/gcc-11' into
Date: Wed, 22 Sep 2021 08:37:26 +0000 (GMT)	[thread overview]
Message-ID: <20210922083726.3D6C13858411@sourceware.org> (raw)

The branch 'devel/omp/gcc-11' was updated to point to:

 80247a54bf5... Merge remote-tracking branch 'origin/releases/gcc-11' into 

It previously pointed to:

 c8d71464699... Fortran: Fix -Wno-missing-include-dirs handling [PR55534]

Diff:

Summary of changes (added commits):
-----------------------------------

  80247a5... Merge remote-tracking branch 'origin/releases/gcc-11' into 
  147d6b7... openmp: Fix OpenMP expansion of scope with non-fallthrugh b
  eeb7829... openmp: Add support for allocator and align modifiers on al
  cc11a17... ipa-fnsummary: Remove inconsistent bp_pack_value (*)
  ae362db... Daily bump. (*)
  da0a562... rs6000: Fix ELFv2 r12 use in epilogue (*)
  5210f05... rs6000: Don't use r12 for CR save on ELFv2 (PR102107) (*)
  7fbab3a... Fortran - (large) arrays in the main shall be static (*)
  d891ef6... Fix no_fsanitize_address effective target (*)
  d4b84ae... Daily bump. (*)

(*) This commit already exists in another branch.
    Because the reference `refs/heads/devel/omp/gcc-11' matches
    your hooks.email-new-commits-only configuration,
    no separate email is sent for this commit.


                 reply	other threads:[~2021-09-22  8:37 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=20210922083726.3D6C13858411@sourceware.org \
    --to=burnus@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: 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).