> I think we also suggested at some point that -O1 optimizations
> shouldn't interfere with debugging too much. But if it is what we did before
> it's certainly fine.
FWIW we have some evidences that -finline-functions-called-once really help
at -O1 in terms of performances (with the 4.5 back-en
On Fri, Jun 10, 2011 at 9:15 PM, Jan Hubicka wrote:
>> On Fri, Jun 10, 2011 at 8:42 PM, Jan Hubicka wrote:
>> > Hi,
>> > by some mistake we enable functions called once at -O0 and it actually
>> > happens from
>> > time to time.
>>
>> Why do it for -O1? It definitely makes debugging less reliab
> On Fri, Jun 10, 2011 at 8:42 PM, Jan Hubicka wrote:
> > Hi,
> > by some mistake we enable functions called once at -O0 and it actually
> > happens from
> > time to time.
>
> Why do it for -O1? It definitely makes debugging less reliable. I'd say do
> it
> for -O[23s] only.
Well, that is wh
On Fri, Jun 10, 2011 at 8:42 PM, Jan Hubicka wrote:
> Hi,
> by some mistake we enable functions called once at -O0 and it actually
> happens from
> time to time.
Why do it for -O1? It definitely makes debugging less reliable. I'd say do it
for -O[23s] only.
Richard.
> Bootstrapped/regtested
Hi,
by some mistake we enable functions called once at -O0 and it actually happens
from
time to time.
Bootstrapped/regtested x86_64-linux, will commit it shortly.
Honza
* opts.c (default_options): Enlist OPT_finline_functions_called_once.
* common.opt (flag_inline_functions_call
