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.8.0-2
Date: Mon, 29 Jun 2026 12:25:50 GMT	[thread overview]
Message-ID: <178273595085.1.12938062497648826161.rpms-gcc-c0371f2be905@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : c0371f2be905364764d229adfe053214c1656ab7
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2013-04-12T15:24:58+02:00
Stats  : +24/-4 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/c0371f2be905364764d229adfe053214c1656ab7?branch=rhel-f41-base

Log:
4.8.0-2

---
diff --git a/.gitignore b/.gitignore
index 98bf870..84fa564 100644
--- a/.gitignore
+++ b/.gitignore
@@ -68,3 +68,4 @@
 /gcc-4.8.0-20130316.tar.bz2
 /gcc-4.8.0-20130320.tar.bz2
 /gcc-4.8.0-20130322.tar.bz2
+/gcc-4.8.0-20130412.tar.bz2

diff --git a/gcc.spec b/gcc.spec
index 88f3ce7..019ce2b 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,9 +1,9 @@
-%global DATE 20130322
-%global SVNREV 196975
+%global DATE 20130412
+%global SVNREV 197896
 %global gcc_version 4.8.0
 # 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 multilib_64_archs sparc64 ppc64 s390x x86_64
 %ifarch %{ix86} x86_64 ia64 ppc ppc64 alpha
@@ -2979,6 +2979,25 @@ fi
 %{_prefix}/libexec/gcc/%{gcc_target_platform}/%{gcc_version}/plugin
 
 %changelog
+* Fri Apr 12 2013 Jakub Jelinek <jakub@redhat.com> 4.8.0-2
+- update from the 4.8 branch
+  - PRs c++/35722, c++/45282, c++/52014, c++/52374, c++/52748, c++/54277,
+	c++/54359, c++/54764, c++/55532, c++/55951, c++/55972, c++/56039,
+	c++/56447, c++/56582, c++/56646, c++/56692, c++/56699, c++/56722,
+	c++/56728, c++/56749, c++/56772, c++/56774, c++/56793, c++/56794,
+	c++/56821, c++/56895, c++/56913, debug/56819, fortran/54932,
+	fortran/56696, fortran/56735, fortran/56737, fortran/56782,
+	libstdc++/55977, libstdc++/55979, libstdc++/56002, libstdc++/56678,
+	libstdc++/56834, lto/56777, middle-end/56694, middle-end/56768,
+	middle-end/56883, other/55274, rtl-optimization/48182,
+	rtl-optimization/56745, sanitizer/55702, target/54805, target/55487,
+	target/56560, target/56720, target/56771, tree-optimization/48184,
+	tree-optimization/48186, tree-optimization/48762,
+	tree-optimization/56407, tree-optimization/56501,
+	tree-optimization/56817, tree-optimization/56837,
+	tree-optimization/56899, tree-optimization/56918,
+	tree-optimization/56920
+
 * Fri Mar 22 2013 Jakub Jelinek <jakub@redhat.com> 4.8.0-1
 - update from the 4.8 branch
   - GCC 4.8.0 release

diff --git a/sources b/sources
index bc2c0ee..ad3fec3 100644
--- a/sources
+++ b/sources
@@ -1,4 +1,4 @@
 be78a47bd82523250eb3e91646db5b3d  cloog-0.18.0.tar.gz
 2659f09c2e43ef8b7d4406321753f1b2  fastjar-0.97.tar.gz
-5dd49f2e3e28c6cf7936b92468020a26  gcc-4.8.0-20130322.tar.bz2
+736cd6277ae8ea1462edd5d0dd7926c4  gcc-4.8.0-20130412.tar.bz2
 bce1586384d8635a76d2f017fb067cd2  isl-0.11.1.tar.bz2

                 reply	other threads:[~2026-06-29 12:25 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=178273595085.1.12938062497648826161.rpms-gcc-c0371f2be905@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