On Tue, 23 Jul 2013, Steve Ellcey wrote:
While doing some space optimization work with mips16 I found that using a
larger case threshold value could shrink the code. I did testing on some
libraries like libpng and libjpeg as well as some test cases I wrote and
came up with 10 as the best
On Tue, 2013-07-30 at 11:18 +0100, Maciej W. Rozycki wrote:
-- it may be that the tests have to be disabled at -Os just like e.g.
code-readable-1.c already is at -O0.
Maciej
Sorry about that, not sure why I didn't notice the failures. Rather
then skipping the tests for -Os I was
On Tue, 30 Jul 2013, Steve Ellcey wrote:
-- it may be that the tests have to be disabled at -Os just like e.g.
code-readable-1.c already is at -O0.
Sorry about that, not sure why I didn't notice the failures. Rather
then skipping the tests for -Os I was thinking it might be better to
Steve Ellcey sell...@mips.com writes:
2013-07-30 Steve Ellcey sell...@mips.com
* gcc.target/mips/code-readable-1.c: Increase switch size.
* gcc.target/mips/code-readable-2.c: Ditto.
* gcc.target/mips/code-readable-3.c: Ditto.
* gcc.target/mips/code-readable-4.c:
While doing some space optimization work with mips16 I found that using a
larger case threshold value could shrink the code. I did testing on some
libraries like libpng and libjpeg as well as some test cases I wrote and
came up with 10 as the best value for space savings in mips16 mode. I did
Steve Ellcey sell...@mips.com writes:
While doing some space optimization work with mips16 I found that using a
larger case threshold value could shrink the code. I did testing on some
libraries like libpng and libjpeg as well as some test cases I wrote and
came up with 10 as the best value
