What does "no optimisation" and "threshold 100" mean? I though if "threshold 100" means that if a literal is > 100 bytes then it is put in
#16190: Speed up handling of large String literals -------------------------------------+------------------------------------- Reporter: hsyl20 | Owner: (none) Type: task | Status: new Priority: normal | Milestone: Component: Compiler | Version: 8.6.3 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by hsyl20): the extra file, then every single line will do that, so the threshold is irrelevant. Indeed with threshold=100 the optimization applies in every tested case to the string literal in the file. I could have written "optimization enable" but then we would have wondered what the threshold was (in particular if the optimization was triggered for small strings).
I wonder why it every slows down? Just the extra file handling?
I guess it's extra file handling (generation and linking) + the traversal of the module bindings. With the small strings, this test seems to be consistently worse with the optimization enabled (i.e. it's not just measure noise). -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/16190#comment:5 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler