https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117455
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Iain Sandoe from comment #11) > Tentatively (absent a way to test this) so long as we continue to link > libgcc, and libgcc provides the heap support, I'd say that's probably OK - > we do not revisit nested lowering later AFAIK. I suppose that if a platform > decided to implement the builtins in a CRT instead of libgcc, then having > the right flag on the link line might matter? Definitively - if the link spec looks at a flag LTO becomes "difficult" and we'd have to enforce the same setting across TUs. Back to the Fortran issue - give that nested functions are standard there, as opposed to C, using heap trampolines by default where supported makes sense. I'm not sure what Ada does here for example, it might just enable execstack explicitly when linking with the Ada driver and thus avoid the diagnostic. > Iain
