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: Possibel gcc Bug when compiling f2c generated C-Code

From: James E Wilson <wilson at specifixinc dot com>
To: Benjamin Schindler <config at gmx dot ch>
Cc: gcc-bugs at gcc dot gnu dot org
Date: Thu, 09 Sep 2004 16:06:47 -0700
Subject: Re: Possibel gcc Bug when compiling f2c generated C-Code
References: <200409091507.19392.config@gmx.ch>

Benjamin Schindler wrote:

CFLAGS="-march=k8 -O2 -pipe -ftracer"
# Above CFLAGS trigger the bug. gcc has also been compiled
# with above flags.

Does the problem go away if you drop the -ftracer option? Does the problem go away if you build gcc normally, i.e. without the -ftracer option? That might be useful info.

On a more general note, we don't track bug reports mailed to the gcc-bugs mailing list. If you want someone to look at this, you should file a bug report into our bugzilla bug database so we can track it. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- Possibel gcc Bug when compiling f2c generated C-Code
  - From: Benjamin Schindler

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