This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/52546] -fstack-usage not working with __attribute__((naked))
- From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 09 Mar 2012 21:48:46 +0000
- Subject: [Bug c/52546] -fstack-usage not working with __attribute__((naked))
- Auto-submitted: auto-generated
- References: <bug-52546-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52546
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-03-09
CC| |ebotcazou at gcc dot
| |gnu.org
Ever Confirmed|0 |1
Severity|normal |enhancement
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-03-09 21:48:46 UTC ---
> 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? :-)