Messages in this thread | | | Date | Wed, 12 Mar 2003 18:14:01 -0500 (EST) | From | Bill Davidsen <> | Subject | Re: 2.5.63 accesses below %esp (was: Re: ntfs OOPS (2.5.63)) |
| |
On Wed, 12 Mar 2003, Linus Torvalds wrote:
> > On Wed, 12 Mar 2003, Szakacsits Szabolcs wrote: > > > > Some data points, in time order. > > > > SuSE 8.0 2.95.3-216 no bug yet [1] > > Debian 3.0 2.95.4-14 no bug yet [1] > > Red Hat 7.[23] 2.96-81 no bug yet [2,3] > > Red Hat 7.[23] 2.96-98 bug introduced [2,3] > > Mandrake 8.1 2.96-0.62mdk bug introduced [4] > > Red Hat 7.[23] 2.96-103 bug fixed [2,3] > > SuSE 8.0 3.0.4 (SuSE) bug fixed [1] > > Mandrake 9.1 3.2.2-2mdk bug fixed [1] > > Ok. So the test really is for one particular version only. > > That's easy. I'll just add a > > #ifdef CONFIG_FRAME_POINTER > #if __GNUC__ == 2 && __GNUC_MINOR__ == 96 > #error This compiler is not safe with frame pointers > #endif > #endif > > to <linux/compiler.h>. Yeah, it will get some fixed compilers too, but > that's just not worth worrying about - people will just have to turn off > CONFIG_FRAME_POINTER and be happy.
Please don't use a hammer on that tack... The Redhat errata gcc (as an example) seems to be fine (see the nice list in the first post) and id's as: oddball:davidsen> gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)
People trying to get 2.5 kernels working want frame pointers and kernel symbols so problems can be reported in a useful way. People running 2.5 kernels are probably more likely to have installed errata.
Perhaps a warning (UNSAFE?) in the config would be better, or whatever else would avoid just blocking the ability to compile a debug kernel.
Yes, I see there's another newer yet gcc, 2.96-113, but it's been working since -103.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |