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-6
Date: Mon, 29 Jun 2026 12:28:55 GMT	[thread overview]
Message-ID: <178273613599.1.16975818984080441579.rpms-gcc-3f45c9c1656e@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : 3f45c9c1656e3a105f589a0accd9a542cff51d92
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2020-10-16T14:04:18+02:00
Stats  : +14/-4 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/3f45c9c1656e3a105f589a0accd9a542cff51d92?branch=rhel-f41-base

Log:
10.2.1-6

---
diff --git a/.gitignore b/.gitignore
index 8032556..736c846 100644
--- a/.gitignore
+++ b/.gitignore
@@ -18,3 +18,4 @@
 /gcc-10.2.1-20200826.tar.xz
 /gcc-10.2.1-20200916.tar.xz
 /gcc-10.2.1-20201005.tar.xz
+/gcc-10.2.1-20201016.tar.xz

diff --git a/gcc.spec b/gcc.spec
index 32ff8c4..51a5a24 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20201005
-%global gitrev 2417bb617beaf81ca86c86977e1589ee77c59a99
+%global DATE 20201016
+%global gitrev b55a9d01144097312b48281486c03e83cf03fde5
 %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 5
+%global gcc_release 6
 %global nvptx_tools_gitrev 5f6f343a302d620b0868edab376c00b15741e39e
 %global newlib_cygwin_gitrev 50e2a63b04bdd018484605fbb954fd1bd5147fa0
 %global _unpackaged_files_terminate_build 0
@@ -3054,6 +3054,15 @@ end
 %endif
 
 %changelog
+* Fri Oct 16 2020 Jakub Jelinek <jakub@redhat.com> 10.2.1-6
+- update from releases/gcc-10 branch
+  - PRs c++/88115, c++/96229, fortran/97272, libstdc++/95788, libstdc++/97273,
+	lto/97290, middle-end/95189, middle-end/95886, rtl-optimization/97313,
+	target/96313, target/96456, target/97150, target/97251, target/97302,
+	target/97349, tree-optimization/97236, tree-optimization/97255,
+	tree-optimization/97357
+  - fix ICE on building Firefox with LTO+PGO (#1886399, PR ipa/97295)
+
 * Mon Oct  5 2020 Jakub Jelinek <jakub@redhat.com> 10.2.1-5
 - update from releases/gcc-10 branch
   - PRs bootstrap/97163, bootstrap/97183, c++/96994, c++/97145, c++/97195,

diff --git a/sources b/sources
index dc303a1..160a0d6 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (gcc-10.2.1-20201005.tar.xz) = f330ba17ed2b3fb3d2eb0f4552055192605d4a762e11e0fdc0b11a29d1309cb36eae60e79863226a0bd51425bde312662272874482748480aad9732770f88f5a
+SHA512 (gcc-10.2.1-20201016.tar.xz) = d324b7c872210a14aabdc117567ae6eff98d40ee8bf7a705a8caf1330d698e167016fb98f095ab56de43140e5f19932775ff3d5757434e3f78f2eec57d3dd1c4
 SHA512 (newlib-cygwin-50e2a63b04bdd018484605fbb954fd1bd5147fa0.tar.xz) = 002a48a7b689a81abbf16161bcaec001a842e67dfbe372e9e109092703bfc666675f16198f60ca429370e8850d564547dc505df81bc3aaca4ce6defbc014ad6c
 SHA512 (nvptx-tools-5f6f343a302d620b0868edab376c00b15741e39e.tar.xz) = f6d10db94fa1570ae0f94df073fa3c73c8e5ee16d59070b53d94f7db0de8a031bc44d7f3f1852533da04b625ce758e022263855ed43cfc6867e0708d001e53c7

                 reply	other threads:[~2026-06-29 12:28 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=178273613599.1.16975818984080441579.rpms-gcc-3f45c9c1656e@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