g++.old-deja/g++.mike/p7325.C - suspected bogus test case

[Zack Weinberg]

Ian Lance Taylor <ian@wasabisystems.com> writes:

> Zack Weinberg <zack@codesourcery.com> writes:
>
>> > (By the way, given this analysis, your stack-frame dumping switch
>> > wouldn't help; the problem is that we don't really have a good method
>> > for saying when the compiler must reuse stack slots and when it must
>> > not.  Probably best to measure the total stack usage of some
>> > representative program(s) -- of which this might be one.)
>> 
>> Good point.  I know this is a critical issue for Linux kernel
>> development, and I would expect it to be the same for embedded
>> environments - both are places where the total available stack 
>> for a thread is very small.  Perhaps we could get some input
>> from people in those domains on how to measure this?
>
> Stack size usage is easy to measure in an execution test.  Is that
> what you are asking?

I had in mind more the static assembly-analysis tests that some people
in Linux kernel development have put together.  However, your quickie
test doesn't look half bad as a replacement for p7325.  It might stop
failing for the wrong reasons, though, if we ever get an optimizer
clever enough to kill the memsets.

zw