[GHC] #10762: On Windows, out-of-codepage characters can cause GHC build to fail

[GHC]

#10762: On Windows, out-of-codepage characters can cause GHC build to fail
---------------------------------+-----------------------------------------
        Reporter:  snoyberg      |                   Owner:  snoyberg
            Type:  bug           |                  Status:  new
        Priority:  normal        |               Milestone:
       Component:  Compiler      |                 Version:  7.10.2
      Resolution:                |                Keywords:
Operating System:  Windows       |            Architecture:  x86_64 (amd64)
 Type of failure:  None/Unknown  |               Test Case:
      Blocked By:                |                Blocking:
 Related Tickets:  #6037         |  Differential Revisions:
---------------------------------+-----------------------------------------

Comment (by Ben Gamari <bgamari.foss@…>):

 In [changeset:"ab9403d5e6eb4f0a2e917d7edcd5821262432b26/ghc"
 ab9403d5/ghc]:
 {{{
 #!CommitTicketReference repository="ghc"
 revision="ab9403d5e6eb4f0a2e917d7edcd5821262432b26"
 Dump files always use UTF8 encoding #10762

 When the Windows codepage or *nix LANG variable is something besides
 UTF-8, dumping to file can cause GHC to exit currently. This changes the
 output encoding for files to match the defined input encoding for
 Haskell source code (UTF-8), making it easier for users and build tools
 to capture this output.

 Test Plan:
 Create a Haskell source file with non-Latin characters for identifier
 names and
 compile with:

 LANG=C ghc -ddump-to-file -ddump-hi filename.hs -fforce-recomp

 Without this patch, it will fail. With this patch, it succeeds

 Reviewers: austin, rwbarton, bgamari

 Reviewed By: bgamari

 Subscribers: thomie

 Differential Revision: https://phabricator.haskell.org/D1151

 GHC Trac Issues: #10762
 }}}

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10762#comment:12>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler