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: 4.9.1-2
Date: Mon, 29 Jun 2026 12:26:21 GMT [thread overview]
Message-ID: <178273598179.1.4907313123014340900.rpms-gcc-4503e5ecde6b@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : 4503e5ecde6b33ccdedd106ff83be138b9b55442
Author : Jakub Jelinek <jakub@redhat.com>
Date : 2014-07-17T11:18:54+02:00
Stats : +12/-6 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/4503e5ecde6b33ccdedd106ff83be138b9b55442?branch=rhel-f41-base
Log:
4.9.1-2
---
diff --git a/.gitignore b/.gitignore
index 2ed88ab..ddfe5c3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -16,3 +16,4 @@
/gcc-4.9.0-20140625.tar.bz2
/gcc-4.9.0-20140702.tar.bz2
/gcc-4.9.1-20140716.tar.bz2
+/gcc-4.9.1-20140717.tar.bz2
diff --git a/gcc.spec b/gcc.spec
index 53716b3..9ce314a 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,9 +1,9 @@
-%global DATE 20140716
-%global SVNREV 212670
+%global DATE 20140717
+%global SVNREV 212747
%global gcc_version 4.9.1
# 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 _unpackaged_files_terminate_build 0
%global _performance_build 1
%global multilib_64_archs sparc64 ppc64 ppc64p7 s390x x86_64
@@ -2798,6 +2798,11 @@ fi
%{_prefix}/libexec/gcc/%{gcc_target_platform}/%{gcc_version}/plugin
%changelog
+* Thu Jul 17 2014 Jakub Jelinek <jakub@redhat.com> 4.9.1-2
+- update from the 4.9 branch
+ - PRs c-family/61741, rtl-optimization/61801, target/61737,
+ tree-optimization/61779
+
* Wed Jul 16 2014 Jakub Jelinek <jakub@redhat.com> 4.9.1-1
- update from the 4.9 branch
- GCC 4.9.1 release
diff --git a/gcc49-libstdc++-docs.patch b/gcc49-libstdc++-docs.patch
index dd328a2..2c8c2b8 100644
--- a/gcc49-libstdc++-docs.patch
+++ b/gcc49-libstdc++-docs.patch
@@ -4,7 +4,7 @@
<a class="link" href="http://www.fsf.org/" target="_top">FSF
</a>
</p><p>
-+ Release 4.9.0
++ Release 4.9.1
+ </p><p>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
@@ -18,7 +18,7 @@
- The API documentation, rendered into HTML, can be viewed online:
+ The API documentation, rendered into HTML, can be viewed here:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
-+ <a class="link" href="api/index.html" target="_top">for the 4.9.0 release, local
++ <a class="link" href="api/index.html" target="_top">for the 4.9.1 release, local
+ </a>
+ </p></li><li class="listitem"><p>
<a class="link" href="http://gcc.gnu.org/onlinedocs/libstdc++/libstdc++-html-USERS-3.4/index.html" target="_top">for the 3.4 release
diff --git a/sources b/sources
index 2167048..a6cce97 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
e34fca0540d840e5d0f6427e98c92252 cloog-0.18.1.tar.gz
-eaa66d3e916b82d819d6b62e6df7e4e5 gcc-4.9.1-20140716.tar.bz2
+0f7586f719b329cfc5e03005e902e9b6 gcc-4.9.1-20140717.tar.bz2
e039bfcfb6c2ab039b8ee69bf883e824 isl-0.12.2.tar.bz2
reply other threads:[~2026-06-29 12:26 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=178273598179.1.4907313123014340900.rpms-gcc-4503e5ecde6b@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