Slashdot Mirror

← Back to Stories (view on slashdot.org)

Pre-Processers for Inlined C Code?

Posted by Cliff on from the taking-two-steps-instead-of-one dept.

Scott Snell asks: "I have inherited the C code for an embedded system project that has run out of code space. The source code is highly fragmented and the compiler doesnt generate efficient code for stack handling. Ideally I would direct the compiler to 'inline' a lot of the functions but unfortunately it doesnt support the inline keyword. Using macros is dangerous and manually inlining is driving me crazy! What I need is a tool that will take the source files, look for the 'inline' keyword and generate new source files that are inlined. Any ideas?"

3 of 62 comments (clear)

  1. Use macros by adb · · Score: 3, Interesting

    Unless I'm on crack, inlining all calls to a function is pretty much the same as replacing the function with a macro. The main difference between inlining and macros would be that the compiler can decide not to inline a function if it doesn't make sense (e.g., if the function is recursive and the compiler isn't up to iterative-izing it), whereas with macros you just can't do recursion safely.

  2. Re:Port it. by aridhol · · Score: 3, Interesting

    I believe the GNU toolchain can generate code for several embedded systems.

    --
    I can't say that I don't give a fuck. I've just run out of fuck to give.
  3. Complete Solution Available by Euphonious+Coward · · Score: 5, Interesting
    Assuming that Gcc doesn't target your platform (otherwise you could just switch to Gcc) you can get an excellent inlining preprocessor from Comeau Computing (look it up on Google), at a very reasonable price.

    Their preprocessor happens also to be a complete C++ compiler. You don't have to use the rest of the C++ features. (You might, for example, want to turn off exception handling.)

    Any half-assed preprocessor that just folds function bodies into line is likely to be much worse than using macros. The worst possible outcome is code that's in some weird private language that only your weird private tools understand. (Cf. Qt/KDE)