Re: [RFC, tentative patch] Adjust cost for conversion expression

2016-11-28 Thread Jeff Law
On 11/24/2016 03:58 AM, Pitchumani Sivanupandi wrote: GCC inlines small functions if the code size after expansion is not excedded. For test case (inline.c, avr-gcc -Os -S inline.c) code size become higher if 'func2' is inlined. It happens because the CONVERT_EXPR/ NOP_EXPR are considered as zero

Re: [RFC, tentative patch] Adjust cost for conversion expression

2016-11-28 Thread Richard Biener
On Mon, 28 Nov 2016, Pitchumani Sivanupandi wrote: > On Thursday 24 November 2016 04:54 PM, Richard Biener wrote: > > On Thu, 24 Nov 2016, Pitchumani Sivanupandi wrote: > > > > > GCC inlines small functions if the code size after expansion is not > > > excedded. > > > For test case (inline.c, avr

Re: [RFC, tentative patch] Adjust cost for conversion expression

2016-11-28 Thread Pitchumani Sivanupandi
On Thursday 24 November 2016 04:54 PM, Richard Biener wrote: On Thu, 24 Nov 2016, Pitchumani Sivanupandi wrote: GCC inlines small functions if the code size after expansion is not excedded. For test case (inline.c, avr-gcc -Os -S inline.c) code size become higher if 'func2' is inlined. It happe

Re: [RFC, tentative patch] Adjust cost for conversion expression

2016-11-24 Thread Richard Biener
On Thu, 24 Nov 2016, Pitchumani Sivanupandi wrote: > GCC inlines small functions if the code size after expansion is not excedded. > For test case (inline.c, avr-gcc -Os -S inline.c) code size become higher if > 'func2' is inlined. It happens because the CONVERT_EXPR/ NOP_EXPR are > considered > a

[RFC, tentative patch] Adjust cost for conversion expression

2016-11-24 Thread Pitchumani Sivanupandi
GCC inlines small functions if the code size after expansion is not excedded. For test case (inline.c, avr-gcc -Os -S inline.c) code size become higher if 'func2' is inlined. It happens because the CONVERT_EXPR/ NOP_EXPR are considered as zero cost expression. Few conversions will cost additio