Date: Fri, 28 Sep 2001 10:05:22 -0500 From: "Matthew Rezny" <mrezny@umr.edu> To: "Andrew Gallatin" <gallatin@cs.duke.edu> Cc: "alpha@freebsd.org" <alpha@freebsd.org> Subject: Re: gcc error compiling KDE2 Message-ID: <20010928150505.1FE5937B40C@hub.freebsd.org> In-Reply-To: <15284.29589.489153.736235@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the info. I have a 21164PC so its EV56 architecture and extentension instructions present are BWX and MVI. Does using -mev56 rather than -mev4 provide a performance increase or does it just help out the problem? On Fri, 28 Sep 2001 08:56:53 -0400 (EDT), Andrew Gallatin wrote: > >Matthew Rezny writes: > > favicons.moc:102: Internal compiler error in `gen_reload_inhi', at > > ../cc_tools/i > >If you have a machine which has the bwx instructions (ev56 or better), >you should put CPUTYPE=ev56 in /etc/make.conf (grep BWX >/var/run/dmesg.boot to see if you have bwx instructions) > >This particular gcc crash goes away with -mev56. In general, gcc >seems to do much better when it is allowed to use the bwx >instructions. > >In fact, even if you don't have a machine that does bwx instructions, >it is safe to turn them on for files that crash gcc -- FreeBSD will >emulate bwx instructions on non-bwx hardware This is slow, but if you >are desparate.. > >FWIW, kde is dog-slow on alpha. Konqueror takes about 45 seconds from >invocation to the first appearance of a window (its the only kde app >running, so it has to start a bunch of kde goop). To switch from the >default file-browser mode it comes up in to a web page takes roughly >20 seconds. This is on a 600MHz UP1000 (ev67) with 450MB free after >Konqueror is launched. > > > >Drew > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010928150505.1FE5937B40C>