[Bug c/52546] -fstack-usage not working with __attribute__((naked))

["marek.vasut at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52546

--- Comment #2 from Marek Vasut <marek.vasut at gmail dot com> 2012-03-09 22:53:04 UTC ---
(In reply to comment #1)
> > Is there any way to tell the compiler how much stack does a naked function
> > consume (or that it consumes zero stack)? Is this a GCC bug?
> 
> It's a limitation.  We could indeed do better, but if you know how much stack
> space the function uses, what's the point in asking the compiler? :-)

Ok, that's understandable and it's a really good function. It'd be certainly
favorable to avoid using such feature (specify how much the function uses), but
exactly for cases like this, it'd be very helpful to have. I'm no GC hacker
myself so I have no idea how much work it'd be to write such a thing and if
it'd be acceptable at all.

Thanks for your quick reply!