aboutsummaryrefslogtreecommitdiff
path: root/test/cases/recursive_inline_function.1.zig
diff options
context:
space:
mode:
authorIsaac Freund <mail@isaacfreund.com>2022-06-09 00:06:16 +0200
committerAndrew Kelley <andrew@ziglang.org>2022-06-09 18:51:43 -0400
commit5816d3eaec3f3bb04e70c89aa402ba9e0e5e7b2c (patch)
tree2cccbd1ac1b95a10823fdd092d3d38ee84b76e8d /test/cases/recursive_inline_function.1.zig
parentf1cff4fa4a28d42ac9055f94ee9a8f7fd2831cd7 (diff)
downloadzig-5816d3eaec3f3bb04e70c89aa402ba9e0e5e7b2c.tar.gz
zig-5816d3eaec3f3bb04e70c89aa402ba9e0e5e7b2c.zip
linker: remove `-z noexecstack` option
Note that the current documentation for the `-z noexecstack` is incorrect. This indicates that an object *does not* require an executable stack. This is actually the default of LLD, and there has never been a way to override this default by passing `-z execstack` to LLD. This commit removes the redundant `-z noexecstack` option from zig build-exe/build-lib/build-obj and ignores the option if passed to zig cc for compatibility. As far as I can tell, there is no reason for code to require an executable stack. This option only exists because the stack was originally executable by default and some programs came to depend on that behavior. Instead, mprotect(2) may be used to make memory pages executable.
Diffstat (limited to 'test/cases/recursive_inline_function.1.zig')
0 files changed, 0 insertions, 0 deletions