Gcc 3.0.4

Gcc 3.0.4

[Bobby McNulty Junior]

Works great!
Working on a Windows XP Home edition now.

Re: GCC 3.0.4

[Mark Mitchell]

> Maybe I miss something, but KDE people still claims that artsd is
> miscompiled. Or this is already fixed?

This is not likely to get fixed in any 3.0 release, but we very much
hope that it will be fixed in GCC 3.1.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

Re: GCC 3.0.4

[Craig Rodrigues]

On Wed, Feb 20, 2002 at 09:45:01AM +0600, Denis Perchine wrote:
> 
> Maybe I miss something, but KDE people still claims that artsd is miscompiled.
> Or this is already fixed?

This has been filed in GNATS as PR 3145:

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?pr=3145&database=gcc&cmd=view

It has been fixed for gcc 3.1, but not in gcc 3.0.4.

There is a patch contributed with the gcc 3.0.x distribution:
gcc/contrib/PR3145.patch.

This patch is not integrated into the gcc 3.0.x distribution,
but can be applied as an optional patch for the end-user.

The patch was not integrated into the 3.0.x releases, because
it was felt that it was too invasive a patch and too risky:
http://gcc.gnu.org/ml/gcc/2002-01/msg01149.html

PR 3145 has been fixed in the gcc 3.1 tree.  gcc 3.1 is
scheduled for release for April 15 (http://gcc.gnu.org/develop.html).

-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@attbi.com

Re: GCC 3.0.4

[Denis Perchine]

Hello,

> At this point, there are no show-stopping problems with GCC 3.0.4.
>
> Therefore, I plan to make the final release sometime tomorrow night.
>
> In you find problems that you think are so critical that we should
> delay the release, please make sure to copy me on the mail personally
> so that I see it as soon as possible.

Maybe I miss something, but KDE people still claims that artsd is miscompiled.
Or this is already fixed?

--
Denis

GCC 3.0.4

[Mark Mitchell]

At this point, there are no show-stopping problems with GCC 3.0.4.

Therefore, I plan to make the final release sometime tomorrow night.

In you find problems that you think are so critical that we should
delay the release, please make sure to copy me on the mail personally
so that I see it as soon as possible.

Thank you,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

Re: GCC 3.0.4

[Mark Mitchell]

--On Monday, February 04, 2002 7:12 PM +0100 Carlo Wood <carlo@alinoe.com> 
wrote:

> On Sun, Feb 03, 2002 at 10:26:12PM -0800, Mark Mitchell wrote:
>> Below, here are the unresolved issues that have been brought to
>> my attention as important bugs to fix for this release.  If you
>
> Did my patch for libiberty make it to this release?

You can easily check that yourself by looking at the current CVS.

If it didn't go in *and it's a regression*, please mail me a pointer
to the patch and a description of the bug it fixes.  (I'm on the
road, so hyperlinks and GNATS references don't do me a whole lot
of good.)

Thanks,

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

Re: GCC 3.0.4

[Richard Henderson]

On Sun, Feb 03, 2002 at 10:26:12PM -0800, Mark Mitchell wrote:
> Richard Henderson <rth@redhat.com>
> 
>   http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00194.html
> 
>   This is a problem with loop unrolling that comes from
>   expand_end_loop incorrectly rotating the loop.  It affects
>   loop-10.c and is a regression from GCC 2.95.

Done on branch.


r~

Re: GCC 3.0.4

[Bob Wilson]

Mark Mitchell wrote:

> Below, here are the unresolved issues that have been brought to
> my attention as important bugs to fix for this release.  If you
> have additional issues, or additional information about these
> issues, please let me know as soon as possible.
> 
> 

> Bob Wilson <bwilson@tensilica.com>
> 
> Would like Xtensa port in GCC 3.0.4.


I added the Xtensa code.  This item is done.

--Bob

Re: GCC 3.0.4

[Eric Christopher]

> "Bradley D. LaRonde" <brad@ltc.com>
> 
>   PR5405 -- 3.0.3 "introduced the -mtune brokenness"
> 

I'll get to this in the next few days.  I'm fixing something else in
mainline at the moment.

-eric

-- 
I will not use abbrev.

Re: GCC 3.0.4

[Carlo Wood]

On Sun, Feb 03, 2002 at 10:26:12PM -0800, Mark Mitchell wrote:
> Below, here are the unresolved issues that have been brought to
> my attention as important bugs to fix for this release.  If you

Did my patch for libiberty make it to this release?
I posted it to patches@ a long time ago and never heard
from it again :/.  Later I asked what happened to my
patch and nobody replied.

http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01047.html

-- 
Carlo Wood <carlo@alinoe.com>

Re: GCC 3.0.4

[Rainer Orth]

Mark Mitchell <mark@codesourcery.com> writes:

> "Richard B. Kreckel" <kreckel@ginac.de>
> 
>   Rainer Orth's patch on Mon Jul 16 2001 broke CLN on Tru64.
> 
>   I requested filing of a PR.

This is PR target/5505 now.  I have not been able to reproduce this yet,
but instead successfully built and tested CLN 1.1.4 from a recent copy of
GCC 3.0.4 20020129.  It may well be that this is an ld bug on the Tru64
UNIX side, in which case we should document requirements for ld/Tru64 UNIX
patches.  Until we can reproduce the problem and make sure the patch really
is the culprit, I suggest we leave the patch in.

	Rainer

Re: GCC 3.0.4

[Zack Weinberg]

On Sun, Feb 03, 2002 at 10:26:12PM -0800, Mark Mitchell wrote:
> Zack Weinberg <zack@codesourcery.com>
> 
>  3.0.3 mishandles #line in the middle of a function, emitting
>  incorrect debugging output.
> 
>  Neil fixed this problem on the mainline.  I asked Zack to apply
>  Neil's patch to the branch, if this is a regression from GCC 2.95.

All the relevant patches for this problem have been applied to the
branch.  Sorry I forgot to notify you.

zw

GCC 3.0.4

[Mark Mitchell]

Please consider the GCC 3.0 branch slushed at this time.  All
code patches will now require my approval, as we are now preparing
for the 3.0.4 release on February 15th.

Unfortunately, I'll be travelling through the 12th.  I'll be
reading email, but sporadically.  My inability to respond may or may
not require a brief postponement of the GCC 3.0.4 release.

Below, here are the unresolved issues that have been brought to
my attention as important bugs to fix for this release.  If you
have additional issues, or additional information about these
issues, please let me know as soon as possible.

Yours,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

"Richard B. Kreckel" <kreckel@ginac.de>

  Rainer Orth's patch on Mon Jul 16 2001 broke CLN on Tru64.

  I requested filing of a PR.

Bob Wilson <bwilson@tensilica.com>

  Would like Xtensa port in GCC 3.0.4.

Don Lindsay <lindsayd@cisco.com>

  PR5198
  PR5143

  There are build failures in cross compilers to AMR and m68k.

"Bradley D. LaRonde" <brad@ltc.com>

  PR5405 -- 3.0.3 "introduced the -mtune brokenness"

Phil Blundell <pb@nexus.co.uk>

  PR5209 -- Bootstrap problem.  Regression from 3.0.2.

Richard Henderson <rth@redhat.com>

  http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00194.html

  This is a problem with loop unrolling that comes from
  expand_end_loop incorrectly rotating the loop.  It affects
  loop-10.c and is a regression from GCC 2.95.

Zack Weinberg <zack@codesourcery.com>

  3.0.3 mishandles #line in the middle of a function, emitting
  incorrect debugging output.

  Neil fixed this problem on the mainline.  I asked Zack to apply
  Neil's patch to the branch, if this is a regression from GCC 2.95.