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] (14 commits) libgomp.texi: Impl. status - non-rect loop nest only partia
Date: Thu, 26 Jan 2023 10:22:35 +0000 (GMT) [thread overview]
Message-ID: <20230126102235.40FFF3858D28@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
f8224dd759f... libgomp.texi: Impl. status - non-rect loop nest only partia
It previously pointed to:
04efab558b8... Update 'libgomp/libgomp.texi' for 'nvptx, libgfortran: Swit
Diff:
Summary of changes (added commits):
-----------------------------------
f8224dd... libgomp.texi: Impl. status - non-rect loop nest only partia
c58f1e1... install.texi: Bump newlib version for nvptx + gcn
8ab86cf... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
6484fc2... restrict gcc.dg/pr107554.c to 64bit platforms (*)
e1a1e1f... Daily bump. (*)
f593bfa... aarch64: fix warning emission for ABI break since GCC 9.1 (*)
3026c53... Daily bump. (*)
50ef4fc... tree-optimization/108164 - undefined overflow with IV vecto (*)
a3dfcaa... tree-optimization/108076 - if-conversion and forced labels (*)
45cff68... middle-end/107994 - ICE after error with comparison gimplif (*)
ca8b819... tree-optimization/107554 - fix ICE in stlen optimization (*)
193f7e6... driver: fix environ corruption after putenv() [PR106624] (*)
7ec291e... Daily bump. (*)
ea99f8d... Fortran: error recovery for invalid CLASS component [PR1084 (*)
(*) 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:[~2023-01-26 10:22 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=20230126102235.40FFF3858D28@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).