#13604: ghci no longer loads dynamic .o files by default if they were built with -O -------------------------------------+------------------------------------- Reporter: George | Owner: dfeuer Type: bug | Status: patch Priority: highest | Milestone: 8.2.2 Component: Compiler | Version: 8.2.1-rc1 Resolution: | Keywords: | RecompilationCheck Operating System: Unknown/Multiple | Architecture: Type of failure: Runtime | Unknown/Multiple performance bug | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D4123 Wiki Page: | -------------------------------------+------------------------------------- Comment (by dfeuer): elaforge, I think I understand kind of what you're asking for now, but there are some tricky questions about the UI. The biggest question is probably how to make interaction with `-fobject-code` sensible. In particular, we don't currently produce object code (ever) when `-fobject- code` is off. So if I type `ghci -O2 A`, where `A` depends on `B`, what should happen if `B` was not compiled `-O2`? Should we generate object code for `B` anyway to obey `-O2`? That seems a bit surprising. Should we load it interpreted? That seems inconsistent. Or perhaps we should change the interpretation of `-fobject-code` in a slightly different direction. What if we make `:load *A` guarantee that it loads `A` interpreted whether or not `A` has been compiled already and whether or not GHCi was run with `-fobject-code`? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/13604#comment:44 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler