From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Buck To: law@cygnus.com Cc: jbuck@Synopsys.COM, zack@rabi.columbia.edu, pfeifer@dbai.tuwien.ac.at, egcs@egcs.cygnus.com Subject: Re: egcs and Linux kernels Date: Wed, 31 Mar 1999 23:46:00 -0000 Message-ID: <199903101944.LAA02316@atrus.synopsys.com> References: <29536.921094521@hurl.cygnus.com> X-SW-Source: 1999-03n/msg00400.html Message-ID: <19990331234600.3QLfcArLYPvHuC_SWf0sUycjBkPbV8GGtHi8ywkI-WE@z> > Right. Basically when gcc-2.7.2 has generated incorrect code they've tweaked > the asms to work around the problem. Over time they end up with a set of > asms that generally works with gcc-2.7.2. > > However, that does not mean they will consistently work over time -- as the > source around the asm changes, the register allocation and reloading needs > will also change, which may again trigger problems. No, because Alan Cox won't release a new 2.0.x kernel until it runs correctly with gcc-2.7.2. Problems may be triggered during development, of course. Kernel and application developers frequently must work with buggy tools, with incomplete knowledge of how those tools work. They must work around the bugs in the compiler, and they won't notice their own bugs if they don't affect the generated executable.