|c code inliner email@example.com (2005-03-31)|
|Re: c code inliner firstname.lastname@example.org (Nathan Moore) (2005-04-02)|
|Re: c code inliner email@example.com (Basile Starynkevitch \[news\]) (2005-04-02)|
|Re: c code inliner firstname.lastname@example.org (2005-04-02)|
|Re: c code inliner email@example.com (Eric Eide) (2005-04-02)|
|Re: c code inliner firstname.lastname@example.org (A Pietu Pohjalainen) (2005-04-26)|
|Re: c code inliner email@example.com (2005-04-30)|
|Re: c code inliner firstname.lastname@example.org (Ira Baxter) (2005-05-04)|
|From:||Nathan Moore <email@example.com>|
|Date:||2 Apr 2005 19:30:18 -0500|
|Posted-Date:||02 Apr 2005 19:30:18 EST|
> Can gcc or cpp produce c code after inlining?
> I.e. I only want my c code after inlining but not compiled.
> Sort of like preprocessing "-E" but with inlining.
> Or any one knows any tools that does only "controlled" inlining?
> I don't need optimization or any thing, just inlining.
Inlining is done on intermediate forms, not on C code.
You could get GCC to give you files with the intermediate form (RTL)
of your programs after inlining has been done, but it you most likely
will not be able to read it.
Why would you need this?
You could use ifdefs to swap out inline functions with macros and then
use the preprocessor.
This is not a complete solution though b/c both inline f() and #define
macros have certain abilities that the other does not.
Why would you want to do this? It is silly.
Return to the
Search the comp.compilers archives again.