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] (13 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Wed, 21 Dec 2022 18:21:27 +0000 (GMT) [thread overview]
Message-ID: <20221221182127.BDD6C3858425@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
38d6201af06... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
10aec76c90d... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Diff:
Summary of changes (added commits):
-----------------------------------
38d6201... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
881fc99... nvptx: reimplement libgomp barriers [PR99555]
7781f30... nvptx: support bar.red instruction
656960a... openmp: Don't try to destruct DECL_OMP_PRIVATIZED_MEMBER va
83f24e7... OpenMP: Duplicate checking for map clauses in Fortran (PR10
c4d7c7e... OpenMP/Fortran: Combined directives with map/firstprivate o
52daccd... libstdc++: Fix unsafe use of dirent::d_name [PR107814] (*)
35ad6ec... libstdc++: Fixes for std::expected (*)
ed3e8a9... libgfortran's ISO_Fortran_binding.c: Use GCC11 version for (*)
93310fe... Daily bump. (*)
1bdb130... d/104749 - document host GDC version requirement (*)
8ac76d5... i386: Avoid fma_chain for -march=alderlake and sapphirerapi (*)
77788d0... 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.
next reply other threads:[~2022-12-21 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 18:21 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-06 7:42 Tobias Burnus
2023-01-16 11:27 Tobias Burnus
2022-09-05 8:18 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=20221221182127.BDD6C3858425@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).