[all-commits] [llvm/llvm-project] 4ed10d: [clang][cmake] Don't pass -fno-strict-aliasing for...

[Sam James via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 4ed10db85919d3d87bf0b3353340b58354a75994
      https://github.com/llvm/llvm-project/commit/4ed10db85919d3d87bf0b3353340b58354a75994
  Author: Sam James <sam at gentoo.org>
  Date:   2025-06-15 (Sun, 15 Jun 2025)

  Changed paths:
    M clang/CMakeLists.txt

  Log Message:
  -----------
  [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.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications