Amar Takhar commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5417#note_137944 How I solved this in my build system was to capture the build output and check for overflow messages from GCC then print a report after. I'm not sure how much of a whack-a-mole this will be. Over time what's "very large" changes. 15 years ago we had this issue between the new boards that had 16 or 32MB? of memory versus 32K I forget the exact numbers but in another 10 years it'll change yet again. I also think just testing via building it is the best way as there's nothing better than actually trying to see if it works there's nothing for us to get wrong. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5417#note_137944 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
