public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] (17 commits) Merge branch 'master' into devel/sphinx
Date: Mon, 31 May 2021 09:31:01 +0000 (GMT) [thread overview]
Message-ID: <20210531093101.0E5063854803@sourceware.org> (raw)
The branch 'devel/sphinx' was updated to point to:
520839b3244... Merge branch 'master' into devel/sphinx
It previously pointed to:
9104f3d64de... Clean up gccgo manual page.
Diff:
Summary of changes (added commits):
-----------------------------------
520839b... Merge branch 'master' into devel/sphinx
21d7bba... LTO: stream properly FUNCTION_DECL_DECL_TYPE. (*)
ef8176e... c++/88601 - [C/C++] __builtin_shufflevector support (*)
df4e035... rs6000: MMA test case ICEs using -O3 [PR99842] (*)
e21e934... Daily bump. (*)
a0a7ade... libstdc++: Remove "Intel Compilers" bibliography entry (*)
a8f588b... Fortran: Fix typo in documentation of BOZ (*)
1a87f83... Daily bump. (*)
ade5ac7... diagnostics: Fix sporadic test failure (*)
12bb62f... [committed][PR bootstrap/100730] Fix warnings in H8 target (*)
f14c9bd... sim: leverage gnulib (*)
5d21c0c... openmp: Add shared to parallel for linear on parallel maste (*)
2364b58... Fix i686 bootstrap by temporarily disabling exporting of gl (*)
4816675... Daily bump. (*)
0f54cc9... tree-iterator: C++11 range-for and tree_stmt_iterator (*)
f7a07f5... tree-optimization/100778 - avoid cross-BB vectorization of (*)
f838e3c... c++: 'this' adjustment for devirtualized call (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/sphinx' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
next reply other threads:[~2021-05-31 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 9:31 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-09 13:30 Martin Liska
2021-08-24 14:43 Martin Liska
2021-04-20 8:02 Martin Liska
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=20210531093101.0E5063854803@sourceware.org \
--to=marxin@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).