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: 9.1.1-2
Date: Mon, 29 Jun 2026 12:28:28 GMT [thread overview]
Message-ID: <178273610890.1.13151175893580799027.rpms-gcc-6919aa138f96@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : 6919aa138f9648a8826b69c79e26ab33f2be3eba
Author : Jakub Jelinek <jakub@redhat.com>
Date : 2019-06-05T15:54:50+02:00
Stats : +19/-45 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/6919aa138f9648a8826b69c79e26ab33f2be3eba?branch=rhel-f41-base
Log:
9.1.1-2
---
diff --git a/.gitignore b/.gitignore
index da7cf68..f56cea7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -76,3 +76,4 @@
/gcc-9.0.1-20190426.tar.xz
/gcc-9.0.1-20190430.tar.xz
/gcc-9.1.1-20190503.tar.xz
+/gcc-9.1.1-20190605.tar.xz
diff --git a/gcc.spec b/gcc.spec
index 92f0ebb..bffb19f 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20190503
-%global SVNREV 270850
+%global DATE 20190605
+%global SVNREV 271961
%global gcc_version 9.1.1
%global gcc_major 9
# 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 1
+%global gcc_release 2
%global nvptx_tools_gitrev c28050f60193b3b95a18866a96f03334e874e78f
%global nvptx_newlib_gitrev aadc8eb0ec43b7cd0dd2dfb484bae63c8b05ef24
%global _unpackaged_files_terminate_build 0
@@ -248,7 +248,6 @@ Patch8: gcc9-foffload-default.patch
Patch9: gcc9-Wno-format-security.patch
Patch10: gcc9-rh1574936.patch
Patch11: gcc9-d-shared-libphobos.patch
-Patch12: gcc9-pr90303.patch
Patch1000: nvptx-tools-no-ptxas.patch
Patch1001: nvptx-tools-build.patch
@@ -765,7 +764,6 @@ to NVidia PTX capable devices if available.
%patch10 -p0 -b .rh1574936~
%endif
%patch11 -p0 -b .d-shared-libphobos~
-%patch12 -p0 -b .pr90303~
cd nvptx-tools-%{nvptx_tools_gitrev}
%patch1000 -p1 -b .nvptx-tools-no-ptxas~
@@ -2957,6 +2955,20 @@ end
%endif
%changelog
+* Wed Jun 5 2019 Jakub Jelinek <jakub@redhat.com> 9.1.1-2
+- update from 9 branch
+ - PRs bootstrap/90543, c++/78010, c++/90173, c++/90265, c++/90383,
+ c++/90484, c++/90532, c++/90548, c++/90572, c++/90598, debug/90197,
+ debug/90733, fortran/54613, fortran/90093, fortran/90329,
+ fortran/90351, fortran/90352, fortran/90355, fortran/90498,
+ gcov-profile/90380, libfortran/90038, libgomp/90527, libgomp/90585,
+ libgomp/90641, libstdc++/81266, libstdc++/90299, libstdc++/90397,
+ libstdc++/90454, libstdc++/90557, libstdc++/90634, libstdc++/90686,
+ libstdc++/90700, pch/90326, sanitizer/90312, sanitizer/90570,
+ target/82920, target/89424, target/89765, target/90357, target/90379,
+ target/90530, target/90547, testsuite/81058, tree-optimization/90385,
+ tree-optimization/90416
+
* Fri May 3 2019 Jakub Jelinek <jakub@redhat.com> 9.1.1-1
- update from 9 branch
- GCC 9.1 release
diff --git a/gcc9-pr90303.patch b/gcc9-pr90303.patch
deleted file mode 100644
index f67c9dd..0000000
--- a/gcc9-pr90303.patch
+++ /dev/null
@@ -1,39 +0,0 @@
-2019-05-03 Jakub Jelinek <jakub@redhat.com>
-
- PR tree-optimization/90303
- * ipa-devirt.c (obj_type_ref_class, get_odr_type): Don't use
- TYPE_CANONICAL for TYPE_STRUCTURAL_EQUALITY_P types in !in_lto_p mode.
-
- * g++.target/i386/pr90303.C: New test.
-
---- gcc/ipa-devirt.c (revision 270834)
-+++ gcc/ipa-devirt.c (revision 270835)
-@@ -2020,7 +2020,7 @@ obj_type_ref_class (const_tree ref)
- ref = TREE_VALUE (TYPE_ARG_TYPES (ref));
- gcc_checking_assert (TREE_CODE (ref) == POINTER_TYPE);
- tree ret = TREE_TYPE (ref);
-- if (!in_lto_p)
-+ if (!in_lto_p && !TYPE_STRUCTURAL_EQUALITY_P (ret))
- ret = TYPE_CANONICAL (ret);
- else
- ret = get_odr_type (ret)->type;
-@@ -2042,7 +2042,7 @@ get_odr_type (tree type, bool insert)
- int base_id = -1;
-
- type = TYPE_MAIN_VARIANT (type);
-- if (!in_lto_p)
-+ if (!in_lto_p && !TYPE_STRUCTURAL_EQUALITY_P (type))
- type = TYPE_CANONICAL (type);
-
- gcc_checking_assert (can_be_name_hashed_p (type)
---- gcc/testsuite/g++.target/i386/pr90303.C (nonexistent)
-+++ gcc/testsuite/g++.target/i386/pr90303.C (revision 270835)
-@@ -0,0 +1,8 @@
-+// PR tree-optimization/90303
-+// { dg-do compile { target ia32 } }
-+// { dg-additional-options "-O2" }
-+
-+struct A { virtual void foo (); };
-+template <class> class B : A {};
-+typedef void (__attribute__((fastcall)) F) ();
-+B<F> e;
diff --git a/sources b/sources
index f5e38f1..ad6a8a4 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (gcc-9.1.1-20190503.tar.xz) = 9787c7f4bc6a2e918cafa5ef0bc21dd29eb88541297168049cffea150d08f50023e6b639bc24fe53daf6f603db286a7a8dd17357d139f0d0cfb3cee2850fee8b
+SHA512 (gcc-9.1.1-20190605.tar.xz) = 05c7624b403e92e455acec9ba3fa2185327de63dbc585fb8f391c522735639b6403cf20555daa50fb0c8ce153f9dfbe7efc1f45b2227f90761a690bfb966ac96
SHA512 (nvptx-newlib-aadc8eb0ec43b7cd0dd2dfb484bae63c8b05ef24.tar.xz) = 94f7089365296f7dfa485107b4143bebc850a81586f3460fd896bbbb6ba099a00217d4042133424fd2183b352132f4fd367e6a60599bdae2a26dfd48a77d0e04
SHA512 (nvptx-tools-c28050f60193b3b95a18866a96f03334e874e78f.tar.xz) = a688cb12cf805950a5abbb13b52f45c81dbee98e310b7ed57ae20e76dbfa5964a16270148374a6426d177db71909d28360490f091c86a5d19d4faa5127beeee1
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=178273610890.1.13151175893580799027.rpms-gcc-6919aa138f96@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