This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: compile time regression, when adding cerr usage

From: James E Wilson <wilson at specifixinc dot com>
To: andre maute <andre dot maute at gmx dot de>
Cc: gcc-bugs at gcc dot gnu dot org
Date: Tue, 27 Jul 2004 11:02:35 -0700
Subject: Re: compile time regression, when adding cerr usage
References: <200407172309.20106.andre.maute@gmx.de> <4105A88A.80504@specifixinc.com> <200407271003.11434.andre.maute@gmx.de>

andre maute wrote:

i already did that, see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613

Thanks. I forgot to check for that. I will add the info I have to the bug report.

-fininline-functions is enabled in -O3 for both gcc-3.3.3 and gcc-3.4.1

Yes, but there are some differences in implementation, and somehow this is causing a problem in gcc-3.4.1.

but not with gcc-3.3.3

I know, you already said that.

Sorry that's wrong, cerr is declared at the beginning of the file and used at the end of the file.

I meant in the average_n functions, cerr is used in between where the variable "a" is declared and when it is used. However, on further review, this turns out not to matter. It doesn't matter where the cerr uses are, only that they exist in the average_n functions.

If you ifdef out the code that writes to cerr, or stop using -finline-functions, the problem goes away. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- compile time regression, when adding cerr usage
  - From: andre maute
- Re: compile time regression, when adding cerr usage
  - From: James E Wilson
- Re: compile time regression, when adding cerr usage
  - From: andre maute

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]