DAE hate optimizations? If yes, AMAA.

OMG OPTIMIZATIONS sometimes make crash dumps fucking unreadable. They even fucking obliterate complete function calls and write the nested function call to the body of the calling function. This is huh... wow!

Back to digg, please.

They even fucking obliterate complete function calls and write the nested function call to the body of the calling function.
that is what inline is supposed to do, especially at O2 and higher

>>3
It's even funnier when the compiler in question (hint: not an x86 compiler) inlines functions that aren't inline'd at all. Basically the functions that get implicitly inlined are those that are called exactly once from a function or two.

    　　 　　　　　　　　　 　／￣∧＿∧￣￣￣ //￣＼＼
    　　　　　　 ＿＿ ⊂／＿＿（´∀｀　）_＿　　/_⊃＿__|　|＼フ ヽ　　CFLAGS JUST KICKED
    　　　,　 ´＿　　／　　　／￣￣ ＿_　／￣　ヽ　　　 __ヽ￣￣　|　　IN, YO!
    　　/∠__／―/-。―／――∠＿／＿_∧　　| 　 　　　 | ∧＿.|　
    　　,========――´=========＝===/⌒ヽ=|.===＝＝| | ヽ￣〕　
    　 |　＿　　 |GENTOO| 　　 ＿ 　″ 　|⌒|　|/　　　_＿ /|　 ）ノ　　　　vroom
    　 ）_旧＿∈≡≡≡≡∋＿旧＿″＿||　ノ丿＿ -――┘ 丿　　　　　　vroom!
    　　 ＼　＼＿ノ ￣￣￣三三三＼　＼＿ノ　　　　三三三三　
    　　　　三三三三三三三三三三三三三三三三三三三三三三三三
    　　　　　　　三三三三三三三三三三三三三三三三三三三三三三三
    　　　　　　　　　　三三三三三三三三三三三三三三三三三三三三三三三三三三
    　　　　　　　　　　　　　　　　　　三三三三三三三三三三三三三三三三三三
    　　　　　　　　　　　　　　　　　　　　　　　　三三三三三三三三三三三

>>4
Doesn't GCC do that too with one of the options?

Clearly it's funrolls time.

>>5
Doesn't GCC do that too with one of the options?