https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88088
--- Comment #15 from Mark Wielaard <mark at gcc dot gnu.org> --- (In reply to Segher Boessenkool from comment #14) > It is very hard to avoid the warning if you use this feature (you need to > stop using the feature altogether!), which would disqualify it for -Wall > immediately Could you give an example of a program where you see -Wtrampolines produce a warning that you believe you cannot easily work around to silence it? In practice I found the warning almost never triggers even in code that uses nested functions a lot since it is only when there is a need to generate executable code on the stack that it shows up. > -Wtrampolines as it currently is does not belong in -Wall. I think it would be more useful if done generically, but I don't mind not adding it to -Wall for targets you feel strongly about should not have it. I just don't know which guard to use to skip targets which explicitly make their stack always executable.
