Date: Wed, 29 Dec 1999 17:02:11 -0800 From: Amancio Hasty <hasty@rah.star-gate.com> To: Bosko Milekic <bmilekic@dsuper.net> Cc: current@FreeBSD.ORG Subject: Re: gcc compile error Message-ID: <199912300102.RAA45553@rah.star-gate.com> In-Reply-To: Your message of "Wed, 29 Dec 1999 19:31:41 EST." <Pine.OSF.4.05.9912291923440.26886-100000@oracle.dsuper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, We just have a buggy version of gcc and it appears that the register allocator is the main problematic area. This is not really a problem for me because what I first try out is a newer version of gcc if I can not get around the compile problem. At any rate remember that at least my reported compiler bug appears to be fixed in the latest gcc-devel port. > > On Wed, 29 Dec 1999, Amancio Hasty wrote: > > !> > !>Without -O or -O2 the program compiles okay. > !> > !>gcc -c bug.c > !> > > Ouch! This looks an awful lot like the last report with `GCC' and > `problem' in the subject. As Matt just mentionned one or two posts ago, > and as I observed in the last thread, have you tried making some of the > variables `volatile?' Assuming of course that the code does compile well > without the optimization flags, one would assume that the "problem" > occurs because of caching of certain variable values in registers (not > that this should be a problem, mind you; one would assume that the > optimization isn't performed too well). > Due to lack of time, and generally speaking, lack of experience with > GCC, I haven't taken a detailed shot at debugging this. > > Bosko. > > -- > Bosko Milekic > Email: bmilekic@dsuper.net > WWW: http://pages.infinit.net/bmilekic/ > -- > > -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912300102.RAA45553>