public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: 4.1.1-2
Date: Mon, 29 Jun 2026 12:22:33 GMT [thread overview]
Message-ID: <178273575304.1.1127599178021069806.rpms-gcc-f7e705b8c7e7@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : f7e705b8c7e7757127c0f09679c48067b4af16d5
Author : Jakub Jelinek <jakub@fedoraproject.org>
Date : 2006-06-12T12:26:12+00:00
Stats : +25/-4 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/f7e705b8c7e7757127c0f09679c48067b4af16d5?branch=rhel-f41-base
Log:
4.1.1-2
---
diff --git a/gcc41.spec b/gcc41.spec
index 6bfc6cb..44d4e45 100644
--- a/gcc41.spec
+++ b/gcc41.spec
@@ -1,6 +1,6 @@
-%define DATE 20060525
+%define DATE 20060612
%define gcc_version 4.1.1
-%define gcc_release 1
+%define gcc_release 2
%define _unpackaged_files_terminate_build 0
%define multilib_64_archs sparc64 ppc64 s390x x86_64
%ifarch %{ix86} x86_64 ia64
@@ -119,7 +119,7 @@ Patch21: gcc41-pr25874.patch
Patch22: gcc41-pr26881.patch
Patch23: gcc41-pr27532.patch
Patch24: gcc41-pr26885.patch
-Patch25: gcc41-pr27758.patch
+Patch25: gcc41-pr27793.patch
Patch26: gcc41-rh192700.patch
Patch27: gcc41-sw2438.patch
%define _gnu %{nil}
@@ -424,7 +424,7 @@ which are required to run programs compiled with the GNAT.
%patch22 -p0 -b .pr26881~
%patch23 -p0 -b .pr27532~
%patch24 -p0 -b .pr26885~
-%patch25 -p0 -b .pr27758~
+%patch25 -p0 -b .pr27793~
%patch26 -p0 -b .rh192700~
%patch27 -p0 -b .sw2438~
@@ -1468,6 +1468,27 @@ fi
%doc rpm.doc/changelogs/libmudflap/ChangeLog*
%changelog
+* Mon Jun 12 2006 Jakub Jelinek <jakub@redhat.com> 4.1.1-2
+- update from gcc-4_1-branch (-r114107:114555)
+ - PRs ada/27769, c++/20173, c++/26068, c++/26433, c++/26496, c++/27177,
+ c++/27385, c++/27447, c++/27451, c++/27601, c++/27713, c++/27716,
+ c++/27722, c++/27801, c++/27806, c++/27807, c++/27819, c/25161,
+ c/26818, c/27020, c/27718, fortran/14067, fortran/16943,
+ fortran/18003, fortran/19015, fortran/19777, fortran/20839,
+ fortran/20877, fortran/23091, fortran/23151, fortran/24168,
+ fortran/24558, fortran/25047, fortran/25058, fortran/25082,
+ fortran/25090, fortran/25098, fortran/25147, fortran/25746,
+ fortran/26551, fortran/27155, fortran/27320, fortran/27411,
+ fortran/27449, fortran/27470, fortran/27524, fortran/27552,
+ fortran/27584, fortran/27613, fortran/27655, fortran/27662,
+ fortran/27709, fortran/27897, libgcj/26483, libgfortran/24459,
+ libgfortran/27757, middle-end/27743, middle-end/27793,
+ target/25758, target/26223, target/27790, target/27842,
+ testsuite/27705, tree-optimization/26242, tree-optimization/26622
+- merge gomp changes from the trunk (-r114518:114520 and -r114524:114525)
+ - PRs preprocessor/27746, c/27747, c++/27748, fortran/27916
+- don't generate decls with the same DECL_UID in C++ FE (PR middle-end/27793)
+
* Thu May 25 2006 Jakub Jelinek <jakub@redhat.com> 4.1.1-1
- update from gcc-4_1-branch (-r113848:114107)
- GCC 4.1.1 release
next reply other threads:[~2026-06-29 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:22 Jakub Jelinek [this message]
2026-06-29 12:22 [rpms/gcc] rhel-f41-base: 4.1.1-2 Jakub Jelinek
2026-06-29 12:22 Jakub Jelinek
2026-06-29 12:22 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=178273575304.1.1127599178021069806.rpms-gcc-f7e705b8c7e7@fedoraproject.org \
--to=jakub@fedoraproject.org \
--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