GCC 3.3 Released

GCC 3.3 Released

[Mark Mitchell]

The GCC 3.3 release is now available from the sites listed at:

 http://www.gnu.org/order/ftp.html

This release contains a very large number of bug-fixes relative to GCC
3.2.3, and a number of new features.  See this page:

 http://gcc.gnu.org/gcc-3.3/changes.html

for a more complete list of changes.

The next release of GCC will be GCC 3.3.1, which will be a bug-fix
release.

As always, there are far too many people involved in the development
and testing of GCC to name them all, but I would like to recognize a
few people whose efforts made it notably easier for me to manage this
release:

In alphabetical order:

- Joe Buck, for producing our release notes.

- Richard Henderson, for reviewing zillions of patches.

- Gerald Pfeifer, for maintaining all of the web documentation.

- Angela Thomas, for putting our CVS repository back together in
  incredibly short order, after I made a mess of it.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

Re: GCC 3.3 Released

[Jie Zhang]

There are four entries for GCC 3.3 release in all ChangeLogs. Like this:

2003-05-13 Release Manager

* GCC 3.3 Released.

2003-05-13 Release Manager

* GCC 3.3 Released.

2003-05-13 Release Manager

* GCC 3.3 Released.

2003-05-13 Release Manager

* GCC 3.3 Released.


- J

Re: GCC 3.3 Released

[Ludovic Brenta]

PR ada/6767 is also fixed in this release.  Is it too late to update
the release notes?

(I haven't been on the gcc list for a while, only on gcc-announce, so
please bear with me if I'm too late in saying this).

--
Ludovic Brenta.

Re: GCC 3.3 Released

[Gerald Pfeifer]

On Thu, 15 May 2003, Jie Zhang wrote:
> There are four entries for GCC 3.3 release in all ChangeLogs. Like this:
>
> 2003-05-13 Release Manager
>

This is due to our releases being automatically created a nice script,
which helps avoid operator error, but unconditionally adds such a
ChangeLog entry for every run.

Mark, I have not tested the patch below, because I'm afraid of wreaking
havoc, but this (or a slight variation thereof) should address the problem.

Gerald

2003-05-15  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* gcc_release (build_sources): Only update ChangeLog files which
	do not yet contain the entry we are going to add.

Index: gcc_release
===================================================================
RCS file: /cvs/gcc/gcc/maintainer-scripts/gcc_release,v
retrieving revision 1.22
diff -u -3 -p -r1.22 gcc_release
--- gcc_release	12 May 2003 21:01:03 -0000	1.22
+++ gcc_release	15 May 2003 14:27:17 -0000
@@ -122,18 +122,23 @@ build_sources() {
            -r ${BRANCH} gcc || \
            error "Could not check out release sources"
     for x in `find ${SOURCE_DIRECTORY} -name ChangeLog`; do
-      cat - ${x} > ${x}.new <<EOF
+      # Update this ChangeLog file only if it does not yet contain the
+      # entry we are going to add.  (This is a safety net for repeated
+      # runs of this script for the same release.)
+      if [ ! grep "GCC ${RELEASE} released." ${x} ]; then
+        cat - ${x} > ${x}.new <<EOF
 ${LONG_DATE}  Release Manager

-	* GCC ${RELEASE} Released.
+	* GCC ${RELEASE} released.

 EOF
-      mv ${x}.new ${x} || \
-        error "Could not update ${x}"
-      (changedir `dirname ${x}` && \
-        ${CVS} ci -m 'Mark ChangeLog' `basename ${x}`) || \
-        error "Could not commit ${x}"
-    done
+        mv ${x}.new ${x} || \
+            error "Could not update ${x}"
+        (changedir `dirname ${x}` && \
+            ${CVS} ci -m 'Mark ChangeLog' `basename ${x}`) || \
+            error "Could not commit ${x}"
+        done
+      fi

     # Update `gcc/version.c'.
     for x in gcc/version.c; do

Re: GCC 3.3 Released

[Mark Mitchell]

On Thu, 2003-05-15 at 07:31, Gerald Pfeifer wrote:
> On Thu, 15 May 2003, Jie Zhang wrote:
> > There are four entries for GCC 3.3 release in all ChangeLogs. Like this:
> >
> > 2003-05-13 Release Manager
> >
> 
> This is due to our releases being automatically created a nice script,
> which helps avoid operator error, but unconditionally adds such a
> ChangeLog entry for every run.
> 
> Mark, I have not tested the patch below, because I'm afraid of wreaking
> havoc, but this (or a slight variation thereof) should address the problem.

Let's give it a try.  Please put it on the mainline.  If you would,
would you also updates release.html to say "For the GCC 3.4 release,
verify that at least one ChangeLog entry has been created by the release
script?"  I'll remove that once 3.4 is out.

Thanks!

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

Re: GCC 3.3 Released

[Joe Buck]

On Thu, May 15, 2003 at 12:37:55PM +0200, Ludovic Brenta wrote:
> PR ada/6767 is also fixed in this release.  Is it too late to update
> the release notes?

I can add it to the web page
http://gcc.gnu.org/gcc-3.3/changes.html

Before I send the patch, are there any other missing bug fixes?

Re: GCC 3.3 Released

[Joseph S. Myers]

On Thu, 15 May 2003, Gerald Pfeifer wrote:

> Mark, I have not tested the patch below, because I'm afraid of wreaking
> havoc, but this (or a slight variation thereof) should address the problem.

You can test this sort of thing against an rsynced copy of the repository
(so it needn't wait for 3.4 to come into effect, or require any artificial
extra entries on the release instructions).

> +      # Update this ChangeLog file only if it does not yet contain the
> +      # entry we are going to add.  (This is a safety net for repeated
> +      # runs of this script for the same release.)
> +      if [ ! grep "GCC ${RELEASE} released." ${x} ]; then
> +        cat - ${x} > ${x}.new <<EOF

A refinement would be that if there's such an entry but with a different
date (if the repeated script runs pass midnight), the date of that entry
gets updated.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

Re: GCC 3.3 Released

[Gerald Pfeifer]

On Thu, 15 May 2003, Mark Mitchell wrote:
>>> There are four entries for GCC 3.3 release in all ChangeLogs. Like this:
> Let's give it a try.  Please put it on the mainline.  If you would,
> would you also updates release.html to say "For the GCC 3.4 release,
> verify that at least one ChangeLog entry has been created by the release
> script?"  I'll remove that once 3.4 is out.

I have now committed the modified patch below...

On Thu, 15 May 2003, Joseph S. Myers wrote:
> You can test this sort of thing against an rsynced copy of the repository
> (so it needn't wait for 3.4 to come into effect, or require any artificial
> extra entries on the release instructions).

...and verified the patch by repeatedly running the script for GCC 3.3.9
and 3.3.10 (locally, of course <g>).

Mark, do you want the note in releasing.html nevertheless?  And should
this go to the 3.3-branch as well to avoid duplicate ChangeLog entries
there?

Gerald

2003-05-24  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* gcc_release (build_sources): Only update ChangeLog files which
	do not yet contain the entry we are going to add.
	Fix typo in added ChangeLog entries.

Index: gcc_release
===================================================================
RCS file: /cvs/gcc/gcc/maintainer-scripts/gcc_release,v
retrieving revision 1.24
diff -u -5 -p -r1.24 gcc_release
--- gcc_release	20 May 2003 11:47:50 -0000	1.24
+++ gcc_release	23 May 2003 22:51:28 -0000
@@ -120,21 +120,26 @@ build_sources() {

     ${CVS} co -d "`basename ${SOURCE_DIRECTORY}`" \
            -r ${BRANCH} gcc || \
            error "Could not check out release sources"
     for x in `find ${SOURCE_DIRECTORY} -name ChangeLog`; do
-      cat - ${x} > ${x}.new <<EOF
+      # Update this ChangeLog file only if it does not yet contain the
+      # entry we are going to add.  (This is a safety net for repeated
+      # runs of this script for the same release.)
+      if ! grep "GCC ${RELEASE} released." ${x} > /dev/null ; then
+        cat - ${x} > ${x}.new <<EOF
 ${LONG_DATE}  Release Manager

-	* GCC ${RELEASE} Released.
+	* GCC ${RELEASE} released.

 EOF
-      mv ${x}.new ${x} || \
-        error "Could not update ${x}"
-      (changedir `dirname ${x}` && \
-        ${CVS} ci -m 'Mark ChangeLog' `basename ${x}`) || \
-        error "Could not commit ${x}"
+        mv ${x}.new ${x} || \
+            error "Could not update ${x}"
+        (changedir `dirname ${x}` && \
+            ${CVS} ci -m 'Mark ChangeLog' `basename ${x}`) || \
+            error "Could not commit ${x}"
+      fi
     done

     # Update `gcc/version.c'.
     for x in gcc/version.c; do
       y=`basename ${x}`