https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115784
--- Comment #2 from Alexey <alexey.lapshin at espressif dot com> --- Hi David, thank you for a quick reply! Maybe it does not critical for high-level applications, that usually don't use "noreturn" functions. In embedded world, it's a common practice to send a reset signal and invoke a forever loop then. Or run a main loop on systems without OS... examples from the real world: https://github.com/espressif/esp-idf/blob/master/components/esp_system/startup.c#L216 https://github.com/espressif/esp-idf/blob/master/components/esp_system/panic.c#L470 https://github.com/espressif/esp-idf/blob/master/components/esp_system/port/brownout.c#L61-L63 But after reading "noreturn" docs once again, there is no relationship between this attribute and the infinity loop that could be applied. So, you could close this ticket, I will just suppress warnings using diagnostic_push/pop mechanism Regards, Alexey
