summaryrefslogtreecommitdiff
path: root/testsuite/tests/driver/all.T
diff options
context:
space:
mode:
authorTamar Christina <tamar@zhox.com>2017-01-15 12:52:14 +0000
committerTamar Christina <tamar@zhox.com>2017-01-15 12:52:14 +0000
commitf63c8ef33ec9666688163abe4ccf2d6c0428a7e7 (patch)
treec6c86e616dd90339594f24fa073e5a98fbdf32ec /testsuite/tests/driver/all.T
parent13a85211040f67977d2a2371f4087d1d2ebf4de4 (diff)
downloadhaskell-f63c8ef33ec9666688163abe4ccf2d6c0428a7e7.tar.gz
Use latin1 code page on Windows for response files.
Summary: D2917 added a change that will make paths on Windows response files use DOS 8.3 shortnames to get around the fact that `libiberty` assumes a one byte per character encoding. This is actually not the problem, the actual problem is that GCC on Windows doesn't seem to support Unicode at all. This comes down to how unicode characters are handled between POSIX and Windows. On Windows, Unicode is only supported using a multibyte character encoding such as `wchar_t` with calls to the appropriate wide version of APIs (name post-fixed with the `W` character). On Posix I believe the standard `char` is used and based on the value it is decoded to the correct string. GCC doesn't seem to make calls to the Wide version of the Windows APIs, and even if it did, it's character representation would be wrong. So I believe GCC just does not support utf-8 paths on Windows. So the hack in D2917 is the only way to get Unicode support. The problem is however that `GCC` is not the only tool with this issue and we don't use response files for every invocation of the tools. Most of the tools probably don't support it. Furthermore, DOS 8.1 shortnames only exist when the path or file physically exists on disk. We pass lots of paths to GCC that don't exist yet, like the output file. D2917 works around this by splitting the path from the file and try shortening that. But this may not always work. In short, even if we do Unicode correctly (which we don't atm, the GCC driver we build uses `char` instead of `wchar_t`) we won't be able to compile using unicode paths that need to be passed to `GCC`. So not sure about the point of D2917. What we can do is support the most common non-ascii characters by writing the response files out using the `latin1` code page. Test Plan: compile + make test TEST=T12971 Reviewers: austin, bgamari, erikd Reviewed By: bgamari Subscribers: thomie, #ghc_windows_task_force Differential Revision: https://phabricator.haskell.org/D2942 GHC Trac Issues: #12971
Diffstat (limited to 'testsuite/tests/driver/all.T')
-rw-r--r--testsuite/tests/driver/all.T2
1 files changed, 1 insertions, 1 deletions
diff --git a/testsuite/tests/driver/all.T b/testsuite/tests/driver/all.T
index d327ac5104..380f28845e 100644
--- a/testsuite/tests/driver/all.T
+++ b/testsuite/tests/driver/all.T
@@ -502,4 +502,4 @@ test('T12752pass', normal, compile, ['-DSHOULD_PASS=1 -Wcpp-undef'])
test('T12955', normal, run_command, ['$MAKE -s --no-print-directory T12955'])
-test('T12971', expect_broken(12971), run_command, ['$MAKE -s --no-print-directory T12971']) \ No newline at end of file
+test('T12971', ignore_stdout, run_command, ['$MAKE -s --no-print-directory T12971'])