public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: 10.2.1-1
Date: Mon, 29 Jun 2026 12:28:47 GMT [thread overview]
Message-ID: <178273612764.1.9518297004492210398.rpms-gcc-ac758fe7b95e@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : ac758fe7b95ea94f328690d6786f0a113f263819
Author : Jakub Jelinek <jakub@redhat.com>
Date : 2020-07-23T11:48:38+02:00
Stats : +39/-8 in 5 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/ac758fe7b95ea94f328690d6786f0a113f263819?branch=rhel-f41-base
Log:
10.2.1-1
---
diff --git a/.gitignore b/.gitignore
index 2fc7303..a1ab839 100644
--- a/.gitignore
+++ b/.gitignore
@@ -13,3 +13,4 @@
/gcc-10.0.1-20200501.tar.xz
/gcc-10.1.1-20200507.tar.xz
/gcc-10.1.1-20200618.tar.xz
+/gcc-10.2.1-20200723.tar.xz
diff --git a/gcc.spec b/gcc.spec
index 5541192..c1d3081 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20200618
-%global gitrev c518050989be3a224a04a8b33d73f37a16c30fbb
-%global gcc_version 10.1.1
+%global DATE 20200723
+%global gitrev 3fc88aa16f1bf661db4518d6d62869f081981981
+%global gcc_version 10.2.1
%global gcc_major 10
# Note, gcc_release must be integer, if you want to add suffixes to
# %%{release}, append them after %%{gcc_release} on Release: line.
-%global gcc_release 2
+%global gcc_release 1
%global nvptx_tools_gitrev 5f6f343a302d620b0868edab376c00b15741e39e
%global newlib_cygwin_gitrev 50e2a63b04bdd018484605fbb954fd1bd5147fa0
%global _unpackaged_files_terminate_build 0
@@ -3009,6 +3009,36 @@ end
%endif
%changelog
+* Thu Jul 23 2020 Jakub Jelinek <jakub@redhat.com> 10.2.1-1
+- update from releases/gcc-10 branch
+ - GCC 10.2 release
+ - PRs bootstrap/94998, c++/90916, c++/95477, c++/95505, c++/95518,
+ c++/95519, c++/95711, c++/95719, c++/95736, c++/95789, c++/95813,
+ c++/95976, c++/96052, c++/96063, c++/96077, c++/96104, c++/96105,
+ c++/96179, c/95141, d/95173, d/95250, debug/95343, fortran/71706,
+ fortran/88379, fortran/93337, fortran/95340, fortran/95366,
+ fortran/95587, fortran/95687, fortran/95688, fortran/95689,
+ fortran/95707, fortran/95708, fortran/95709, fortran/95743,
+ fortran/95812, fortran/95826, fortran/95827, fortran/95828,
+ fortran/95829, fortran/95880, fortran/95881, fortran/95978,
+ ipa/12345, ipa/93223, ipa/96040, ipa/96130, libstdc++/91153,
+ libstdc++/91807, libstdc++/94087, libstdc++/94627, libstdc++/94936,
+ libstdc++/95282, libstdc++/95851, libstdc++/95915, lto/91576,
+ lto/95604, middle-end/94600, middle-end/94964, middle-end/95114,
+ middle-end/95118, middle-end/95270, middle-end/95493,
+ middle-end/95690, middle-end/95810, middle-end/95903,
+ middle-end/96194, target/12345, target/93224, target/93492,
+ target/94791, target/94891, target/95018, target/95105, target/95347,
+ target/95581, target/95683, target/95713, target/95726, target/95874,
+ target/96001, target/96125, target/96174, testsuite/96180,
+ tree-optimization/90838, tree-optimization/94969,
+ tree-optimization/95049, tree-optimization/95110,
+ tree-optimization/95133, tree-optimization/95308,
+ tree-optimization/95487, tree-optimization/95638,
+ tree-optimization/95717, tree-optimization/95804,
+ tree-optimization/95857, tree-optimization/96075,
+ tree-optimization/96133, tree-optimization/96146
+
* Thu Jun 18 2020 Jakub Jelinek <jakub@redhat.com> 10.1.1-2
- update from releases/gcc-10 branch
- PRs c++/90212, c++/90479, c++/90915, c++/91529, c++/92103, c++/92633,
diff --git a/gcc10-libstdc++-docs.patch b/gcc10-libstdc++-docs.patch
index cf881d8..d51b6d3 100644
--- a/gcc10-libstdc++-docs.patch
+++ b/gcc10-libstdc++-docs.patch
@@ -4,7 +4,7 @@
<a class="link" href="https://www.fsf.org" target="_top">FSF
</a>
</p><p>
-+ Release 10.1.1
++ Release 10.2.1
+ </p><p>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
@@ -17,7 +17,7 @@
</p><p>
- The API documentation, rendered into HTML, can be viewed online
+ The API documentation, rendered into HTML, can be viewed locally
-+ <a class="link" href="api/index.html" target="_top">for the 10.1.1 release</a>,
++ <a class="link" href="api/index.html" target="_top">for the 10.2.1 release</a>,
+ online
<a class="link" href="http://gcc.gnu.org/onlinedocs/" target="_top">for each GCC release</a>
and
diff --git a/sources b/sources
index 9a9bb69..0e888d0 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (gcc-10.1.1-20200618.tar.xz) = 7dbec01ce5199c37072f97874b11b59b9e5a5b20d9782f662eb856c34009faeb1644e39fb7f13e8c8e016ad552d9c9fcf5d5ba9562297dccf66ebc75f1b963cf
+SHA512 (gcc-10.2.1-20200723.tar.xz) = e1719e4a18f43bb76acb91c0d768711e78d7e8c478b72e691911094e233570597997ed108ba7ed4fb136542993af935ea38ec462a1972689c9220d4cc0e2933f
SHA512 (newlib-cygwin-50e2a63b04bdd018484605fbb954fd1bd5147fa0.tar.xz) = 002a48a7b689a81abbf16161bcaec001a842e67dfbe372e9e109092703bfc666675f16198f60ca429370e8850d564547dc505df81bc3aaca4ce6defbc014ad6c
SHA512 (nvptx-tools-5f6f343a302d620b0868edab376c00b15741e39e.tar.xz) = f6d10db94fa1570ae0f94df073fa3c73c8e5ee16d59070b53d94f7db0de8a031bc44d7f3f1852533da04b625ce758e022263855ed43cfc6867e0708d001e53c7
diff --git a/update-gcc.sh b/update-gcc.sh
index 89d0859..c04b746 100755
--- a/update-gcc.sh
+++ b/update-gcc.sh
@@ -3,5 +3,5 @@
git clone --depth 1 git://gcc.gnu.org/git/gcc.git gcc-dir.tmp
git --git-dir=gcc-dir.tmp/.git fetch --depth 1 origin $1
d=`date --iso | sed 's/-//g'`
-git --git-dir=gcc-dir.tmp/.git archive --prefix=gcc-10.1.1-$d/ $1 | xz -9e > gcc-10.1.1-$d.tar.xz
+git --git-dir=gcc-dir.tmp/.git archive --prefix=gcc-10.2.1-$d/ $1 | xz -9e > gcc-10.2.1-$d.tar.xz
rm -rf gcc-dir.tmp
next reply other threads:[~2026-06-29 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:28 Jakub Jelinek [this message]
2026-06-29 12:28 [rpms/gcc] rhel-f41-base: 10.2.1-1 Jakub Jelinek
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=178273612764.1.9518297004492210398.rpms-gcc-ac758fe7b95e@fedoraproject.org \
--to=jakub@redhat.com \
--cc=git-commits@fedoraproject.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