On Thu, Sep 21, 2017 at 2:27 AM, Chris Johns <chr...@rtems.org> wrote:
> On 20/09/2017 15:08, Chris Johns wrote: > > > > Is it worth running? I am wondering about hard coding a filter to not > run it in > > rtems-test runs. > > > > I have add test failure exceptions and minimum is the only hard coded > entry. If > this test runs and does not time out it is marked as a pass. > The intent of this test is to demonstrate the smallest executable and data size possible. Looking at the sizes on a few BSPs this morning, I wonder why it is so large: text data bss dec hex filename 45792 880 3088 49760 c260 erc32/.../minimum.exe 49344 888 6896 57128 df28 jmr3904/.../minimum.exe 66000 1220 16709968 16777188 ffffe4 psim/.../minimum.exe 76832 1008 268341188 268419028 fffbfd4 xilinx_zynq_a9_qemu/.../minimum.exe Any ideas where the large .text size is coming from? --joel > > Chris > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
