Re: About loop unrolling and optimize for size

2015-09-20 Thread Simon Schubert
de besides > makes possibly debugging harder? > > Thanks/Fredrik > > > > From: Richard Biener [richard.guent...@gmail.com] > Sent: Friday, August 14, 2015 09:28 > To: sa...@hederstierna.com > Cc: gcc@gcc.gnu.org > Subject: Re: About loop unrolling

RE: About loop unrolling and optimize for size

2015-08-14 Thread sa...@hederstierna.com
sibly debugging harder? Thanks/Fredrik From: Richard Biener [richard.guent...@gmail.com] Sent: Friday, August 14, 2015 09:28 To: sa...@hederstierna.com Cc: gcc@gcc.gnu.org Subject: Re: About loop unrolling and optimize for size On Thu, Aug 13, 2015

Re: About loop unrolling and optimize for size

2015-08-14 Thread Richard Biener
On Thu, Aug 13, 2015 at 6:26 PM, sa...@hederstierna.com wrote: > Hi > I'm using an ARM thumb cross compiler for embedded systems and always do > optimize for small size with -Os. > > Though I've experimented with optimization flags, and loop unrolling. > > Normally loop unrolling is always bad fo

About loop unrolling and optimize for size

2015-08-13 Thread sa...@hederstierna.com
Hi I'm using an ARM thumb cross compiler for embedded systems and always do optimize for small size with -Os. Though I've experimented with optimization flags, and loop unrolling. Normally loop unrolling is always bad for size, code is duplicated and size increases. Though I discovered that in