[nasm:nasm-2.15.xx] configure.ac: -enable-... breaks other compilers, so hope for clang 10

[nasm-bot for H. Peter Anvin (Intel)]

Commit-ID:  70f0d04ee50a18e78c30ce6c6fc4f32427724793
Gitweb:     http://repo.or.cz/w/nasm.git?a=commitdiff;h=70f0d04ee50a18e78c30ce6c6fc4f32427724793
Author:     H. Peter Anvin (Intel) <hpa at zytor.com>
AuthorDate: Mon, 6 Jul 2020 11:30:22 -0700
Committer:  H. Peter Anvin (Intel) <hpa at zytor.com>
CommitDate: Mon, 6 Jul 2020 11:30:22 -0700

configure.ac: -enable-... breaks other compilers, so hope for clang 10

The -enable-... option to enable -ftrivial-auto-var-init=zero breaks
linking not just on clang but on other compilers (gcc) too. Drop it;
this feature is enabled by default in clang 10.

Signed-off-by: H. Peter Anvin (Intel) <hpa at zytor.com>


---
 configure.ac | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/configure.ac b/configure.ac
index a6ee5d3f..b101f46c 100644
--- a/configure.ac
+++ b/configure.ac
@@ -86,18 +86,12 @@ dnl specified first.  Enable this so this script can actually discover
 dnl which -W options are possible for this compiler.
 PA_ADD_CFLAGS([-Werror=unknown-warning-option])
 
-dnl Without this option, clang sometimes fail to link if LDFLAGS is
-dnl a superset of CFLAGS, which is the normal thing...
-PA_ADD_CFLAGS([-Wno-unused-command-line-argument])
-
 dnl Force gcc and gcc-compatible compilers treat signed integers
 dnl as 2's complement
 PA_ADD_CFLAGS([-fwrapv])
 
 dnl Force clang to behave in a predictable manner, in order to make bugs
 dnl possible to track down. gcc appears to have this behavior by default.
-dnl Needing the -enable-... option is kind of a bizarre thing.
-PA_ADD_CFLAGS([-enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang])
 PA_ADD_CFLAGS([-ftrivial-auto-var-init=zero])
 
 dnl Some environments abuse __STRICT_ANSI__ to disable some