> It also seems like rather than checking for ebpf on files with large
> stacks, we should be using the generic mechanisms to defined the
allowed
> size of the stack (mentioned in prior review) & mark test which use
too
> much space. This would almost certainly help other embedded targets
as
> well.
>
> I first thought about doing that, but hesitated when I realized it would
> require to alter existing tests in no trivial ways: will the test still
> effectively test whatever it is supposed to test, after the size of an
> array is changed, for example?
I think you just add something like
/* dg-require-stack-size "<size>" */
Assuming that's right you don't have to worry about changing the test
itself and potentially changing its meaning.
I wouldn't necessarily try to figure the exact size needed by each test.
A reasonable guesstimation ought to be sufficient.
Oh nice, I didn't know about that directive.
Thanks!
