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: 7.0.1-0.3
Date: Mon, 29 Jun 2026 12:27:17 GMT [thread overview]
Message-ID: <178273603746.1.9145312931986355876.rpms-gcc-557c86d25cc6@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : 557c86d25cc63c2dcf74603e6592f1f0c52dca25
Author : Jakub Jelinek <jakub@redhat.com>
Date : 2017-01-28T08:26:07+01:00
Stats : +13/-4 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/557c86d25cc63c2dcf74603e6592f1f0c52dca25?branch=rhel-f41-base
Log:
7.0.1-0.3
---
diff --git a/.gitignore b/.gitignore
index 04f9095..8b9f440 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
/gcc-7.0.1-20170126.tar.bz2
/nvptx-newlib-aadc8eb0ec43b7cd0dd2dfb484bae63c8b05ef24.tar.bz2
/nvptx-tools-c28050f60193b3b95a18866a96f03334e874e78f.tar.bz2
+/gcc-7.0.1-20170128.tar.bz2
diff --git a/gcc.spec b/gcc.spec
index 1be797b..d97310a 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20170126
-%global SVNREV 244932
+%global DATE 20170128
+%global SVNREV 245003
%global gcc_version 7.0.1
%global gcc_major 7
# 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 0.2
+%global gcc_release 0.3
%global nvptx_tools_gitrev c28050f60193b3b95a18866a96f03334e874e78f
%global nvptx_newlib_gitrev aadc8eb0ec43b7cd0dd2dfb484bae63c8b05ef24
%global _unpackaged_files_terminate_build 0
@@ -3232,6 +3232,14 @@ fi
%endif
%changelog
+* Sat Jan 28 2017 Jakub Jelinek <jakub@redhat.com> 7.0.1-0.3
+- update from the trunk
+ - PRs c++/64382, c++/68727, c++/78771, c++/79176, debug/78835, debug/79129,
+ libstdc++/79190, libstdc++/79243, libstdc++/79254,
+ rtl-optimization/78559, rtl-optimization/79194, target/65484,
+ target/79131, target/79239, tree-optimization/71374,
+ tree-optimization/79244, tree-optimization/79245
+
* Thu Jan 26 2017 Jakub Jelinek <jakub@redhat.com> 7.0.1-0.2
- update from the trunk
- PRs bootstrap/79132, bootstrap/79198, c++/71290, c++/71406, c++/71710,
diff --git a/sources b/sources
index dc15801..b7253bc 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (gcc-7.0.1-20170126.tar.bz2) = 472cb6cb2ec235b603402a0086f79f46741aa84ba5385707dba64f0e0442f0bcfcfb3bc77c8b061c484c18ccb8f18afb71e393fc39fc350219ecd0b9c6749777
+SHA512 (gcc-7.0.1-20170128.tar.bz2) = 41edc3cd3cf59816aa8f6f5c410a6c5a0332eadf65d0ccd478367767c17d909462280f439a9a96b61c72d447b17caa8b5fa0ddea22c25a79be2fd63675088e49
SHA512 (nvptx-newlib-aadc8eb0ec43b7cd0dd2dfb484bae63c8b05ef24.tar.bz2) = 38f97c9297ad108568352a4d28277455a3c01fd8b7864e798037e5006b6f757022e874bbf3f165775fe3b873781bc108137bbeb42dd5ed3c7d3e6747746fa918
SHA512 (nvptx-tools-c28050f60193b3b95a18866a96f03334e874e78f.tar.bz2) = 95b577a06a93bb044dbc8033e550cb36bcf2ab2687da030a7318cdc90e7467ed49665e247dcafb5ff4a7e92cdc264291d19728bd17fab902fb64b22491269330
next reply other threads:[~2026-06-29 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:27 Jakub Jelinek [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-29 12:27 [rpms/gcc] rhel-f41-base: 7.0.1-0.3 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=178273603746.1.9145312931986355876.rpms-gcc-557c86d25cc6@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