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] (14 commits) Merge remote-tracking branch 'origin/releases/gcc-11' into
Date: Mon, 6 Sep 2021 13:31:06 +0000 (GMT) [thread overview]
Message-ID: <20210906133106.37EF63858023@sourceware.org> (raw)
The branch 'devel/omp/gcc-11' was updated to point to:
a5643a2981b... Merge remote-tracking branch 'origin/releases/gcc-11' into
It previously pointed to:
4c086e7dabf... 'libgomp.c/target-43.c': '-latomic' for nvptx offloading
Diff:
Summary of changes (added commits):
-----------------------------------
a5643a2... Merge remote-tracking branch 'origin/releases/gcc-11' into
57f6800... tree-optimization/102046 - fix SLP build from scalars with (*)
7f584a3... tree-optimization/101925 - fix VN with reverse storage orde (*)
3f29e30... middle-end/101824 - properly handle volatiles in nested fn (*)
54cbe85... Daily bump. (*)
71013e5... Fortran - extend set of substring expressions handled in le (*)
c94755c... Fortran - simplify length of substring with constant bounds (*)
b18391e... Daily bump. (*)
9c3a475... Daily bump. (*)
f826c25... Fortran - correct check for constraint F2008:C628 / F2018:C (*)
95553bf... Fortran - fix whitespace issue during parsing of assigned g (*)
1456e63... Use UNSPSEC_XXSPLTIDP instead of UNSPEC_XXSPLTID (*)
c464a94... Make xxsplti*, xpermx, xxeval be vecperm type. (*)
d9f215a... Fix tests that require IBM 128-bit long double (*)
(*) 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.
next reply other threads:[~2021-09-06 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 13:31 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-02 15:01 Tobias Burnus
2021-06-08 8:15 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=20210906133106.37EF63858023@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).