https://github.com/thesamesam updated https://github.com/llvm/llvm-project/pull/144222
>From 4ed10db85919d3d87bf0b3353340b58354a75994 Mon Sep 17 00:00:00 2001 From: Sam James <s...@gentoo.org> Date: Sat, 14 Jun 2025 14:07:14 +0100 Subject: [PATCH] [clang][cmake] Don't pass -fno-strict-aliasing for GCC This was added a long time ago.. * to the Makefiles in 40fee6313df688d43d1f8bbe85bc35161689afca; * first to CMake in b3ce035c7155644d5bced46c45ae5ac865b7aedc; * then moved to only apply when building Clang with GCC in c5635a6af7c643169f81145bfae8c895f2207792. This shouldn't be needed these days. If an issue does arise, it really ought to be documented better and the cause will certainly be different than it was back then. The two GCC bugs cited in 40fee6313df688d43d1f8bbe85bc35161689afca were: * https://gcc.gnu.org/PR41874 * https://gcc.gnu.org/PR41838 and both are long-fixed. Not only that, if those issues did come up again, we'd be better off doing -Wno-strict-aliasing where appropriate if there weren't a real code issue or some suppression that was tighter in scope wasn't appropriate. --- clang/CMakeLists.txt | 3 --- 1 file changed, 3 deletions(-) diff --git a/clang/CMakeLists.txt b/clang/CMakeLists.txt index ab2ac9bc6b9ad..94607a8e8473c 100644 --- a/clang/CMakeLists.txt +++ b/clang/CMakeLists.txt @@ -345,9 +345,6 @@ configure_file( # Add appropriate flags for GCC if (LLVM_COMPILER_IS_GCC_COMPATIBLE) set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-common -Woverloaded-virtual") - if (NOT "${CMAKE_CXX_COMPILER_ID}" MATCHES "Clang") - set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-strict-aliasing") - endif () # Enable -pedantic for Clang even if it's not enabled for LLVM. if (NOT LLVM_ENABLE_PEDANTIC) _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
