Re: executable stacks, a few suggetions

H. Peter Anvin (hpa@transmeta.com)
Mon, 14 Apr 1997 16:40:54 -0700 (PDT)

> Why not decide that gcc is broken as long as it uses trampolines
> without adding explicit code to first make the stack executable ?

Because you don't want to be able to turn stack execution on once it
has been disabled. Better is to have a function to turn it off, and
as a bonus old code will still work.

I am very concerned about the portability implications of this,
though.

-hpa