It seems the gcc3.2 ignores -fomit-frame-pointer, without giving any diagnostics about it. I had noticed it with some of my software *breaking* because of that as some assembler parts were trying to access %ebp then.
This may affect the mdk9 *kernel* itself - usally the linux kernel should be compiled with -fomit-frame-pointer, and a quick dissassemble-check on some modules/drivers showed a standard stackframe now. Perhaps some other option enforced a standard stackframe but traditionally it means that the kernel is *slowed* down in this mode. Are no-omit-frame-pointer/use-standard-stackframe intentional? It is atleast beyond my expections, so I'm issuing it as a warning-flashlight - I haven't found notice of it in general gcc docs, so is that only a behaviour of the mdk gcc3? $ gcc --version gcc (GCC) 3.2 (Mandrake Linux 9.0 3.2-1mdk) -- cheers, guido (not subscribed to cooker ML)
