https://sourceware.org/bugzilla/show_bug.cgi?id=29072
--- Comment #14 from Nick Clifton <nickc at redhat dot com> --- (In reply to H.J. Lu from comment #12) > I don't think we should issue a warning in this case: Why not ? The original point of this PR was that an application can gain an executable stack without the programmer being aware of it, simply because an object file in the link requests one. Providing a warning, along with the name of the object file to blame, will allow the builder to decide if they are OK with this, possibly unexpected, behaviour. > Shouldn't compiler issue the warning instead? Maybe - that is up to the compiler designers. But the purpose of this warning is to let application builders know that their app now has a major security risk, and it may be because of an object file in a library and nothing at all to do with files that they themselves maintain. -- You are receiving this mail because: You are on the CC list for the bug.
