This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/19748] aggressive no-inline options still cause inlining
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Feb 2005 02:00:30 -0000
- Subject: [Bug c++/19748] aggressive no-inline options still cause inlining
- References: <20050202015319.19748.yuri@tsoft.com>
- Reply-to: gcc-bugzilla 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