This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] start of C binary compatibility testsuite
Janis Johnson wrote:
> > > bash-2.05$ size c_compat_main_tst.o c_compat_x_tst.o c_compat_y_tst.o
> > > text data bss dec hex filename
> > > 28 0 0 28 1c c_compat_main_tst.o
> > > 349200 0 0 349200 55410 c_compat_x_tst.o
> > > 117272 0 0 117272 1ca18 c_compat_y_tst.o
> It doesn't look as if splitting them up that way will reduce stack
> requirements so I'll try other things, using an sh-elf cross compiler
> for testing. What's a reasonable stack limit for tests?
Well, the problem is actually not the amount of stack usage, but the
total usage of text + data + bss + stack.
When you look at the above figures, you'll see that the size of the
text section is considerable. Reducing this to about a third should
make these tests fit easily into 256K, maybe even into 192K (the
latter is the default setting for the SH simulator in the dejagnu
framework, although that is too small for many C++ tests).
Note, we've used the macro STACK_SIZE even for tests where the issue
was with the size of other sections because we don't have a generic macro
for the available memory, but STACK_SIZE had already been intruduced
relatively early, so it was available.
--
--------------------------
SuperH (UK) Ltd.
2410 Aztec West / Almondsbury / BRISTOL / BS32 4QX
T:+44 1454 465658