Re: Compiler error XFree86-Server

2002-08-10 Thread Marc Recht
> Yes. But our 5.0-RELEASE is will non-polished; so I think having the > compiler in the same shape is OK if it means we can get bugs fixed and > our needs taken care of. But it's still a relase. :-) > Many IA-64, and AMD x86-64 bug fixes and improvements aren't merged back > to the 3.{1,2} bran

Re: Compiler error XFree86-Server

2002-08-09 Thread David O'Brien
On Fri, Aug 09, 2002 at 09:26:32PM +0200, Marc Recht wrote: > > IMO going to 3.3 would be much better -- we can actually get our needs > > better addressed as the compiler is still in development, but about to > > head into code slush. We cannot affect GCC 3.2.1 too much due to it > > being on a

Re: Compiler error XFree86-Server

2002-08-09 Thread Marc Recht
> You might want to try the attached code-snippet I grabbed from the gcc > GNATS. It manages to ICE 3.1 and 3.2 with a lot of optimizations, > including pentium2/3/4 and athlon-* and is believed to trigger the same > bug that borks XFree86 here. XFree works fine (for me) with -O -march=athlon-x

Re: Compiler error XFree86-Server

2002-08-09 Thread Marc Recht
> > > system compiler would make bug reports from -CURRENT users even more useful. > > Indeed. IMHO going to 3.2 is the best we could do. > > IMO going to 3.3 would be much better -- we can actually get our needs > better addressed as the compiler is still in development, but about to > head into

Re: Compiler error XFree86-Server

2002-08-09 Thread Michael Nottebrock
David O'Brien wrote: >>>I've got suggests that it's still present in all branches. I get the >>>impression that not too many people really use gcc3 with heavy >>>optimization on big stuff like XFree86 yet ... Of course, updating the >> >>XFree86 works like a charm built with -march=athlon-xp .

Re: Compiler error XFree86-Server

2002-08-09 Thread David O'Brien
On Fri, Aug 09, 2002 at 08:13:55AM +0200, Marc Recht wrote: > > Because chances are good that the bugs still aren't fixed. I reported a > > bug related to optimization with -march=athlon recently and the reply > If you've got a newer Athlon (XP) then you could compile it with -march=athlon-xp. >

Re: Compiler error XFree86-Server

2002-08-08 Thread Marc Recht
> Because chances are good that the bugs still aren't fixed. I reported a > bug related to optimization with -march=athlon recently and the reply If you've got a newer Athlon (XP) then you could compile it with -march=athlon-xp. I've filed a PR with a patch against bsd.cpu.mk (misc/41425) recent

Re: Compiler error XFree86-Server

2002-08-08 Thread Michael Nottebrock
David O'Brien wrote: > On Wed, Aug 07, 2002 at 03:59:47PM +0200, Michael Nottebrock wrote: > >>>Please submit a full bug report, >>>with preprocessed source if appropriate. >>>See http://www.gnu.org/software/gcc/bugs.html> for instructions. >>>*** Error code 1 >>> >>>Stop in >>>/usr/ports/x11-se

Re: Compiler error XFree86-Server

2002-08-08 Thread David O'Brien
On Wed, Aug 07, 2002 at 03:59:47PM +0200, Michael Nottebrock wrote: > >Please submit a full bug report, > >with preprocessed source if appropriate. > >See http://www.gnu.org/software/gcc/bugs.html> for instructions. > >*** Error code 1 > > > >Stop in > >>/usr/ports/x11-servers/XFree86-4-Server/w