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-4
Date: Mon, 29 Jun 2026 12:28:53 GMT [thread overview]
Message-ID: <178273613365.1.17104649212265453767.rpms-gcc-6b90f867141f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : 6b90f867141f55a8bd001ee3d708098afb203fad
Author : Jakub Jelinek <jakub@redhat.com>
Date : 2020-09-16T11:51:20+02:00
Stats : +12/-36 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/6b90f867141f55a8bd001ee3d708098afb203fad?branch=rhel-f41-base
Log:
10.2.1-4
---
diff --git a/gcc.spec b/gcc.spec
index 22001c7..40d011c 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -269,13 +269,12 @@ Patch9: gcc10-Wno-format-security.patch
Patch10: gcc10-rh1574936.patch
Patch11: gcc10-d-shared-libphobos.patch
Patch12: gcc10-pr96383.patch
-Patch13: gcc10-pr96385.patch
-Patch14: gcc10-pr96690.patch
-Patch15: gcc10-pr96939.patch
-Patch16: gcc10-pr96939-2.patch
-Patch17: gcc10-pr96939-3.patch
-Patch18: gcc10-pr97032.patch
-Patch19: gcc10-pr97060.patch
+Patch13: gcc10-pr96690.patch
+Patch14: gcc10-pr96939.patch
+Patch15: gcc10-pr96939-2.patch
+Patch16: gcc10-pr96939-3.patch
+Patch17: gcc10-pr97032.patch
+Patch18: gcc10-pr97060.patch
# On ARM EABI systems, we do want -gnueabi to be part of the
# target triple.
@@ -788,13 +787,12 @@ to NVidia PTX capable devices if available.
%endif
%patch11 -p0 -b .d-shared-libphobos~
%patch12 -p0 -b .pr96383~
-%patch13 -p0 -b .pr96385~
-%patch14 -p0 -b .pr96690~
-%patch15 -p0 -b .pr96939~
-%patch16 -p0 -b .pr96939-2~
-%patch17 -p0 -b .pr96939-3~
-%patch18 -p0 -b .pr97032~
-%patch19 -p0 -b .pr97060~
+%patch13 -p0 -b .pr96690~
+%patch14 -p0 -b .pr96939~
+%patch15 -p0 -b .pr96939-2~
+%patch16 -p0 -b .pr96939-3~
+%patch17 -p0 -b .pr97032~
+%patch18 -p0 -b .pr97060~
find gcc/testsuite -name \*.pr96939~ | xargs rm -f
echo 'Red Hat %{version}-%{gcc_release}' > gcc/DEV-PHASE
diff --git a/gcc10-pr96385.patch b/gcc10-pr96385.patch
deleted file mode 100644
index 22fe68e..0000000
--- a/gcc10-pr96385.patch
+++ /dev/null
@@ -1,22 +0,0 @@
-2020-08-03 Richard Biener <rguenther@suse.de>
-
- PR lto/96385
-libiberty/
- * simple-object-elf.c
- (simple_object_elf_copy_lto_debug_sections): Localize global
- UNDEFs and reuse the prevailing name.
-
---- libiberty/simple-object-elf.c
-+++ libiberty/simple-object-elf.c
-@@ -1467,6 +1467,11 @@ simple_object_elf_copy_lto_debug_sections (simple_object_read *sobj,
- && st_shndx < shnum
- && pfnret[st_shndx - 1] == -1)
- discard = 1;
-+ /* We also need to remove global UNDEFs which can
-+ cause link fails later. */
-+ else if (st_shndx == SHN_UNDEF
-+ && ELF_ST_BIND (*st_info) == STB_GLOBAL)
-+ discard = 1;
-
- if (discard)
- {
next reply other threads:[~2026-06-29 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:28 Jakub Jelinek [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-29 12:28 [rpms/gcc] rhel-f41-base: 10.2.1-4 Jakub Jelinek
2026-06-29 12:28 Jakub Jelinek
2026-06-29 12:28 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=178273613365.1.17104649212265453767.rpms-gcc-6b90f867141f@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