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-12] (7 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Wed, 28 Sep 2022 07:53:35 +0000 (GMT)	[thread overview]
Message-ID: <20220928075335.EE67F3858438@sourceware.org> (raw)

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

 b1caa1db9d3... Merge branch 'releases/gcc-12' into devel/omp/gcc-12

It previously pointed to:

 87caae2e83f... amdgcn: Add builtin for vectorized DFmode fabs operation

Diff:

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

  b1caa1d... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
  8dbde52... Daily bump. (*)
  36c23b3... c-family: Drop nothrow from c_keywords (*)
  7cb8784... Daily bump. (*)
  be18783... Daily bump. (*)
  a0d5241... Daily bump. (*)
  c9bb2be... Daily bump. (*)

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

             reply	other threads:[~2022-09-28  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  7:53 Tobias Burnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-23  8:29 Tobias Burnus
2022-08-03 12:17 Tobias Burnus

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=20220928075335.EE67F3858438@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).