Related articles |
---|
c code inliner paulw@mmail.ath.cx (2005-03-31) |
Re: c code inliner nathan.moore@sdc.cox.net (Nathan Moore) (2005-04-02) |
Re: c code inliner basile-news@starynkevitch.net (Basile Starynkevitch \[news\]) (2005-04-02) |
Re: c code inliner tmk@netvision.net.il (2005-04-02) |
Re: c code inliner eeide@cs.utah.edu (Eric Eide) (2005-04-02) |
Re: c code inliner pohjalai@cc.helsinki.fi (A Pietu Pohjalainen) (2005-04-26) |
Re: c code inliner gtoal@gtoal.com (2005-04-30) |
Re: c code inliner idbaxter@semdesigns.com (Ira Baxter) (2005-05-04) |
From: | "Basile Starynkevitch \[news\]" <basile-news@starynkevitch.net> |
Newsgroups: | comp.compilers |
Date: | 2 Apr 2005 19:31:50 -0500 |
Organization: | http://starynkevitch.net - Ours |
References: | 05-03-122 |
Keywords: | C |
Posted-Date: | 02 Apr 2005 19:31:50 EST |
On 2005-04-01, paulw@mmail.ath.cx <paulw@mmail.ath.cx> wrote:
> Hi
>
> Can gcc or cpp produce c code after inlining?
> I.e. I only want my c code after inlining but not compiled.
This does not have much sense. Inlining is interleaved with
optimisation. And the result of optimisation is some internal compiler
representation which is not always representable in C.
If you use gcc4 (not yet released, ie the latest CVS snapshot of gcc)
you might ask a printable output of the Gimple representation of code.
If (with gcc) you want a function to be always inlined, declare it
static inline __attribute__ ((__always_inline__))
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net
aliases: basile<at>tunes<dot>org = bstarynk<at>nerim<dot>net
8, rue de la Faïencerie, 92340 Bourg La Reine, France
Return to the
comp.compilers page.
Search the
comp.compilers archives again.