rmk@arm.linux.org.uk said:
> and then read kernel/fork.s ? Yes, some people who care about getting
> the best out of the kernel do convert C to assembly and then read the
> result. If there's something really yucky in there, then you go back
> and fix it in the C source.
s/C/compiler/
Or were you _really_ advocating the kind of development methodology which
gave us all those gotos to out-of-line code which gcc helpfully moved back
in-line for us when it got a little smarter because someone else observed
the same problem and fixed it _properly_?
Tweaking your code and sacrificing chickens until you happen to get the
output you want is no substitute for fixing the compiler. And it's a waste
of good chickens.
-- dwmw2- 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/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:22 EST