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-13] (20 commits) Merge branch 'releases/gcc-13' into devel/omp/gcc-13
Date: Tue, 17 Oct 2023 08:38:12 +0000 (GMT) [thread overview]
Message-ID: <20231017083813.2CAC6385828D@sourceware.org> (raw)
The branch 'devel/omp/gcc-13' was updated to point to:
d56305c421a9... Merge branch 'releases/gcc-13' into devel/omp/gcc-13
It previously pointed to:
36e5f02e64bd... Fortran/OpenMP: Fix handling of strictly structured blocks
Diff:
Summary of changes (added commits):
-----------------------------------
d56305c... Merge branch 'releases/gcc-13' into devel/omp/gcc-13
2b9957c... Fortran's gfc_match_char: %S to match symbol with host_asso
cc87aae... rs6000: Use default target option node for callee by defaul (*)
4d22de9... rs6000: Skip empty inline asm in rs6000_update_ipa_fn_targe (*)
8ae7823... Daily bump. (*)
3aaa6d4... Daily bump. (*)
a9f3986... Daily bump. (*)
1c2bd08... Do not add partial equivalences with no uses. (*)
c23aa9a... Daily bump. (*)
f37fae5... LibF7: Implement atan2. (*)
162a537... Daily bump. (*)
f0efc4b... Ensure float equivalences include + and - zero. (*)
16a4df2... tree-ssa-strlen: optimization skips clobbering store [PR111 (*)
5c65cec... Daily bump. (*)
8a5fe7f... ada: Fix infinite loop with multiple limited with clauses (*)
97fbb39... Daily bump. (*)
452a69c... Daily bump. (*)
f3c2d8b... Daily bump. (*)
add2afa... MATCH: Fix infinite loop between `vec_cond(vec_cond(a,b,0), (*)
e9e0b9e... Daily bump. (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/omp/gcc-13' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2023-10-17 8:38 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=20231017083813.2CAC6385828D@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).