#10560: -f and -O options interact in non-obvious, order dependent ways -------------------------------------+------------------------------------- Reporter: bgamari | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.10.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Incorrect | Unknown/Multiple warning at compile-time | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+------------------------------------- Comment (by svenpanne): I would even go further than Joachim in comment 3: I would open a ticket if the commandline arguments were *not* order-dependent, this is by far the most common way of doing things for lots of tools/compilers. I would even object to the idea of emitting a warning if something is overridden, even in the case of meta flags like -Ox (might be OK to enable the warning by another flag, but definitely not by default). Warnings are part of the "API" of a compiler, and I bet many automatic builds would be broken by such an ad-hoc change for no good reason. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10560#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler