On 2012-08-29 5:37 PM, Bastian Bittorf wrote: >> Disabling all optimization sounds like a horrible idea to me. How >> about >> identifying which specific optimization is causing this issue? If > > if you follow the thread, you can see it: > https://lists.olsr.org/pipermail/olsr-dev/2012-August/006056.html > > problem1: > for filing a bug-report we need to know mips and arm-assembler. Not necessarily.
> problem2: > it needs some time to fix the bug and > to replace our linaro-gcc with the fixed one > > better larger binaries, than non-working binaries. > for now i'am ok with only omit "-Os" for olsrd* > > affected archs are definitely some brcm47xx-boards, > some ARM and some atheros-SoC-boards. I'm strongly opposed to hiding bugs, because it usually leads to people forgetting about them, and regressions showing up once people clean up hackery much later. Did you read/understand my suggestion of identifying the specific optimization that is triggering the error? gcc has lots of -f flags related to optimization which are controlled by -O*. Find out which one is causing the error and we're much closer to having a proper fix (and we could even add a cflag (with a helpful comment) to disable that specific optimization without bloating up the entire binary. - Felix _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
