This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/15366] [unit-at-a-time] -fno-inline-functions is ignored for static functions
- From: "jh at suse dot cz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Aug 2004 23:01:48 -0000
- Subject: [Bug rtl-optimization/15366] [unit-at-a-time] -fno-inline-functions is ignored for static functions
- References: <20040510152002.15366.nigel@mips.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jh at suse dot cz 2004-08-19 23:01 -------
Subject: Re: [unit-at-a-time] -fno-inline-functions is ignored for static functions
>
> ------- Additional Comments From mmitchel at gcc dot gnu dot org 2004-08-19 21:12 -------
> I'd like to know why this is considered a desirable feature.
>
> It changes long-standing behavior of GCC, and means that you now have to add
> -fkeep-inlinine-functions if you need those static functions to be callable from
> the debugger, etc.
>
> Jan, at the very least, the documentation needs to change.
This is what we ended up after discussion with Richard. Technically
inlining functions called once is different optimization than normal
inlining in a way that it can't lose code size (well except for
degenerating some optimizer). I originally had separate flag for
handling that one, but I would be happy with any sollution
(ie updating documetnation, making -fno-inline-functions to disable the
inlininf called once too or having -fno-inline-functions-called-once)
What would be the preferrence?
Honza
>
> --
> What |Removed |Added
> ----------------------------------------------------------------------------
> AssignedTo|unassigned at gcc dot gnu |jh at suse dot cz
> |dot org |
> Status|NEW |ASSIGNED
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15366
>
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15366