summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormortimer <mortimer@openbsd.org>2019-06-01 15:20:08 +0000
committermortimer <mortimer@openbsd.org>2019-06-01 15:20:08 +0000
commit70dbe2957938f0a4b14a60c4c5ae9a0d4ec2b5a6 (patch)
treeb6ad0cea0c804c37542321d34edbe943272b7a58
parentRevert to using the SCHED_LOCK() to protect time accounting. (diff)
downloadwireguard-openbsd-70dbe2957938f0a4b14a60c4c5ae9a0d4ec2b5a6.tar.xz
wireguard-openbsd-70dbe2957938f0a4b14a60c4c5ae9a0d4ec2b5a6.zip
Do not eliminate frame pointers on i386. The entire i386 ecosystem assumes
it will be there. problem found by naddy@, "heck yeah" kettenis@
-rw-r--r--gnu/llvm/tools/clang/lib/Driver/ToolChains/Clang.cpp1
1 files changed, 0 insertions, 1 deletions
diff --git a/gnu/llvm/tools/clang/lib/Driver/ToolChains/Clang.cpp b/gnu/llvm/tools/clang/lib/Driver/ToolChains/Clang.cpp
index 06e98b7c403..64a84051474 100644
--- a/gnu/llvm/tools/clang/lib/Driver/ToolChains/Clang.cpp
+++ b/gnu/llvm/tools/clang/lib/Driver/ToolChains/Clang.cpp
@@ -532,7 +532,6 @@ static bool useFramePointerForTargetByDefault(const ArgList &Args,
switch (Triple.getArch()) {
case llvm::Triple::mips64:
case llvm::Triple::mips64el:
- case llvm::Triple::x86:
case llvm::Triple::x86_64:
return !areOptimizationsEnabled(Args);
default: