Muli Ben-Yehuda <[EMAIL PROTECTED]> writes: > I was thinking of kernel compilation, which requires -O2 (force > inlining)
-O3 turns -finline-functions on. -O2 turns -fforce-mem on, maybe that's what you meant. > and thus would break horribly if you compile some of the files with > O1. Why? Why should compilation of different files affect each other? Do you mean that the *kernel* (as opposed to compilation) would break horribly at run time if compiled without -O2? I am not even sure that Nadav's comment regarding profiling is correct. I strongly suspect that if I cannot link together code compiled with different flags it is either a compiler or a library bug. I must admit that off the top of my head I don't recall a situation where I had to compile my code with different flags. -- Oleg Goldshmidt | [EMAIL PROTECTED] ================================================= "We work by wit, and not by witchcraft, And wit depends on dilatory time." ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
