Date: Tue, 27 Jul 1999 00:02:40 +0200 To: "pgcc AT delorie DOT com" Subject: Re: Compling Kernals with PGCC Message-ID: <19990727000240.H12035@cerebro.laendle> Mail-Followup-To: "pgcc AT delorie DOT com" References: <19990726093526 DOT D19462 AT cerebro DOT laendle> <19990726204832 DOT VXNX8809 DOT mail DOT rdc1 DOT il DOT home DOT com AT mercury DOT snydernet DOT lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19990726204832.VXNX8809.mail.rdc1.il.home.com@mercury.snydernet.lan>; from Steve Snyder on Mon, Jul 26, 1999 at 03:48:27PM -0400 X-Operating-System: Linux version 2.2.10 (root AT cerebro) (gcc driver version egcs-2.91.66 19990314 (egcs-1.1.2 release) executing gcc version 2.7.2.3) From: Marc Lehmann Reply-To: pgcc AT delorie DOT com X-Mailing-List: pgcc AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, Jul 26, 1999 at 03:48:27PM -0400, Steve Snyder wrote: > > >* glibc also needs fixes for the next gcc and pgcc version, I recommened to > > use the following cflags until this is done: > > -D__NO_MATH_INLINES -D__NO_STRING_INLINES > > I knew that string inlines were a problem with egcs v1.1.2. Are math > inlines also a problem with egcs, or is that a pgcc-specific problem? Some math inlines have similar problems (with the upcoming gcc and pgcc releases). At the moment I wouldn't trust anything that contains unchecked asm()'s or other low-level (gcc-specific) trickery. The problem is much worse with pgcc: where egcs might create correct code by pure chance pgcc has a much higher probability to create incorrect (garbage in garbage out). -- -----==- | ----==-- _ | ---==---(_)__ __ ____ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / pcg AT goof DOT com |e| -=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |