Re: Getting a broken program when the -funroll-loops flag is set (gcc linaro arm)

Hi Michael, Thanks for looking into that issue. Upgrading to GCC 4.7 might be possible, for now I've decided to remove the -funroll-loops flag, and keep working with Freescale's GCC 4.6.2 build. Mickey. - Original Message - From: Michael Hope michael.h...@linaro.org To: Mickey Iluz

Re: Getting a broken program when the -funroll-loops flag is set (gcc linaro arm)

On 14 November 2012 22:09, Mickey Iluz mickey.i...@orcam.com wrote: Hi Michael, Thanks for looking into that issue. Upgrading to GCC 4.7 might be possible, for now I've decided to remove the -funroll-loops flag, and keep working with Freescale's GCC 4.6.2 build. Sure. I also found that

Getting a broken program when the -funroll-loops flag is set (gcc linaro arm)

Hi, I've encountered a case where gcc produces a broken program: a branch that should never be taken is taken, and wrong values are written to memory (and printed out). The code is fairly ordinary and small. It can be seen here: http://pastebin.com/0Hspz8mw This happens when -funroll-loops