lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master acfa77b0 08/17: Simplify


From: Greg Chicares
Subject: [lmi-commits] [lmi] master acfa77b0 08/17: Simplify
Date: Sat, 2 Jul 2022 21:42:14 -0400 (EDT)

branch: master
commit acfa77b0556d88da8e47d9de24d3fda5b1a561a4
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Simplify
    
    The code to decide whether '-fomit-frame-pointer' must be used with
    MinGW-w64 is too complicated and confusing. Because ".0" is appended
    to $(gcc_version), it can never match "10" exactly.
    
    The debian-testing ("bookworm") MinGW-w64 gcc version is still 10.0.0
    after all this time, and there's no newer version in "sid" today. It
    seems unlikely ever to match 10.2.1 exactly: e.g., it may advance to
    10.4 in a single jump.
    
    Thus, expunged the innermost condition: it's unlikely ever to be
    helpful, and it's confusing.
---
 compiler_gcc.make | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/compiler_gcc.make b/compiler_gcc.make
index 00887078..1a1b78ae 100644
--- a/compiler_gcc.make
+++ b/compiler_gcc.make
@@ -117,9 +117,6 @@ ifneq (,$(filter $(gcc_version), 10 10.0))
 # Fixed in gcc-10.2.1, but this makefile doesn't detect the last
 # component of major.minor.patchlevel reliably.
     tutelary_flag := -fomit-frame-pointer
-    ifneq (,$(filter $(gcc_version), 10 10.2.1))
-      tutelary_flag := -fno-omit-frame-pointer
-    endif
   endif
 endif
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]