http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52546
Bug #: 52546 Summary: -fstack-usage not working with __attribute__((naked)) Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassig...@gcc.gnu.org ReportedBy: marek.va...@gmail.com Dear GCC hackers, I get the following output while compiling my code (isolated snippet follows): spl_mem_init.c: In function 'data_abort_memdetect_handler': spl_mem_init.c:180:1: warning: -fstack-usage not supported for this target [enabled by default] Culprit: void data_abort_memdetect_handler(void) __attribute__((naked)); void data_abort_memdetect_handler(void) { asm volatile("subs pc, r14, #4"); } gcc --version arm-linux-gnueabi-gcc (Debian 4.6.2-14) 4.6.2 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Though this is observed also with stock GCC 4.6. 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? Thanks in advance!