The 4.1 branch is now open for changes under the usual regression-only
rules for release branches.
Here are the changes that I commited during the release process.
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
2007-02-14 Mark Mitchell [EMAIL PROTECTED]
* DEV-PHASE: Set to prerelease.
* BASE-VER: Increment.
Index: DEV-PHASE
===
--- DEV-PHASE (revision 121944)
+++ DEV-PHASE (working copy)
@@ -0,0 +1 @@
+prerelease
Index: BASE-VER
===
--- BASE-VER(revision 121944)
+++ BASE-VER(working copy)
@@ -1 +1 @@
-4.1.2
+4.1.3
Index: htdocs/gcc-4.1/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.1/changes.html,v
retrieving revision 1.22
diff -c -5 -p -r1.22 changes.html
*** htdocs/gcc-4.1/changes.html 21 Mar 2006 11:19:31 - 1.22
--- htdocs/gcc-4.1/changes.html 14 Feb 2007 04:32:10 -
***
*** 9,18
--- 9,21
--
body
h1GCC 4.1 Release Seriesbr /Changes, New Features, and Fixes/h1
+ pThe latest release in the 4.1 release series is
+ a href=#4.1.2GCC 4.1.2/a./p
+
h2Caveats/h2
h2General Optimizer Improvements/h2
ul
***
*** 663,669
--- 666,708
various buffer overflow (and format string) vulnerabilities. Compared
to the mudflap bounds checking feature, the safe builtins have far
smaller overhead. This means that programs built using safe builtins
should not experience any measurable slowdown./li
/ul
+
+ h2a name=4.1.2GCC 4.1.2/a/h2
+
+ pThis is the a
+
href=http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVEDamp;resolution=FIXEDamp;target_milestone=4.1.2;list
+ of problem reports (PRs)/a from GCC's bug tracking system that are
+ known to be fixed in the 4.1.2 release. This list might not be
+ complete (that is, it is possible that some PRs that have been fixed
+ are not listed here)./p
+
+ p
+ When generating code for a shared library, GCC now recognizes that
+ global functions may be replaced when the program runs. Therefore,
+ it is now more conservative in deducing information from the bodies
+ of functions. For example, in this example:
+
+ pre
+ void f() {}
+ void g() {
+ try { f(); }
+ catch (...) {
+cout Exception;
+ }
+ }
+ /pre
+
+ G++ would previously have optimized away the catch clause, since it
+ would have concluded that codef/code cannot throw exceptions.
+ Because users may replace codef/code with another function in
+ the main body of the program, this optimization is unsafe, and is no
+ longer performed. If you wish G++ to continue to optimize as
+ before, you must add a codethrow()/code clause to the
+ declaration of codef/code to make clear that it does not throw
+ exceptions.
+ /p
+
/body
/html
Index: htdocs/gcc-4.1/index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.1/index.html,v
retrieving revision 1.5
diff -c -5 -p -r1.5 index.html
*** htdocs/gcc-4.1/index.html 27 May 2006 20:55:34 - 1.5
--- htdocs/gcc-4.1/index.html 14 Feb 2007 04:32:10 -
***
*** 6,26
body
h1GCC 4.1 Release Series/h1
! pMay 24, 2006/p
pThe a href=http://www.gnu.org;GNU project/a and the GCC
! developers are pleased to announce the release of GCC 4.1.1./p
pThis release is a bug-fix release, containing fixes for regressions
! in GCC 4.1.0 relative to previous releases of GCC./p
h2Release History/h2
dl
dtGCC 4.1.1/dt
dda name=4.1.1May 24, 2006/a
(a href=changes.htmlchanges/a)
/dd
--- 6,32
body
h1GCC 4.1 Release Series/h1
! pFebruary 13, 2007/p
pThe a href=http://www.gnu.org;GNU project/a and the GCC
! developers are pleased to announce the release of GCC 4.1.2./p
pThis release is a bug-fix release, containing fixes for regressions
! in GCC 4.1.1 relative to previous releases of GCC./p
h2Release History/h2
dl
+ dtGCC 4.1.2/dt
+ dda name=4.1.2February 13, 2007/a
+ (a href=changes.html#4.1.2changes/a)
+ /dd
+
+ dl
dtGCC 4.1.1/dt
dda name=4.1.1May 24, 2006/a
(a href=changes.htmlchanges/a)
/dd
Index: htdocs/gcc-4.1/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.1/changes.html,v
retrieving revision 1.23
diff -c -5 -p -r1.23 changes.html
*** htdocs/gcc-4.1/changes.html 14 Feb 2007 04:32:44 - 1.23
--- htdocs/gcc-4.1/changes.html 14 Feb 2007 04:36:22 -
*** are not listed here)./p
*** 681,701
p
When generating code for a shared library, GCC now recognizes that
global functions may be replaced when the program runs. Therefore,
it is now more conservative in deducing
