[PATCH] Add writeFileWithSystemEncoding to LibLLVMSupport

Rafael Auler rafaelauler at gmail.com
Thu Aug 14 15:06:23 PDT 2014


>
>
>
> Do you have a complete list of programs that require the current
> codepage to be used? If it is jut gcc, it seems better to switch clang
> to using ld directly instead of calling gcc for linking. From the
> perspective of this patch it would mean marking gcc as not supporting
> response files.
>
> IIRC my conclusion was that all GNU programs running on Windows uses the
current codepage, which would mean that binutils is also on this category.
But I will re-investigate this matter to be sure.


> Since the function may write UTF8, UTF16 and native codepage, what
> about calling it just writeFileWithEncoding and pass an
> UTF8/UTF16/CurrentCP enum value to it? The unix version can just
> assert that it is always passed UTF8.
>
> Sounds great, I will implement this change.

Regards,
Rafael Auler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140814/e31d5c9e/attachment.html>


More information about the llvm-commits mailing list