[Bug c++/19748] aggressive no-inline options still cause inlining

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-02-02 02:00 -------
(In reply to comment #2)
> Also note sometimes when a function is pure/const it can be removed which is why it might act as 
> inlining.
This is an example where we remove the function call so it looks like inlining:
void f(void) {}
void g(void)
{
  f();
}
But we are not inlining here at all, we just removed the function as the function is pure/const.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19748