austin says: In general I think we should actively move this to an autoconf check
#9678: Warning about __sync_fetch_and_nand semantics from gcc -------------------------------------+------------------------------------- Reporter: gintas | Owner: Type: bug | Status: new Priority: low | Milestone: Component: Build System | Version: 7.9 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: None/Unknown | Unknown/Multiple Blocked By: | Test Case: Related Tickets: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by thomie): * priority: normal => low * status: patch => new * differential: Phab:D334 => Comment: that then sets ghc-options appropriately, based on if the C compiler specified actually supports this flag or not. This will be much more robust in general, I think.
gintas says: Makes sense. Probably more trouble than it's worth, that warning should get dropped from gcc eventually...
-- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/9678#comment:4 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler