This is an archive of the discontinued LLVM Phabricator instance.

(Part 1/2) non-Unicode response file on Windows: UTF-8 BOM
ClosedPublic

Authored by ygao on Jan 23 2015, 3:44 PM.

Details

Reviewers
rnk
Summary

Hi all,
This is spun off from D7133, based on Rafael's suggestion that the UTF-8 BOM changes should be in its separate patch.
In the process of writing a regression test case, I looked at what was done for UTF-16 BOM, and tried to add a similar unit test for UTF-8 BOM in the same file, but this also means that hasUTF8ByteOrderMark() needs be exposed as an external function instead of a static helper function. I hope that is okay.

  • Gao

Diff Detail

Event Timeline

ygao updated this revision to Diff 18696.Jan 23 2015, 3:44 PM
ygao retitled this revision from to (Part 1/2) non-Unicode response file on Windows: UTF-8 BOM.
ygao updated this object.
ygao edited the test plan for this revision. (Show Details)
ygao added subscribers: Unknown Object (MLST), rnk, majnemer and 4 others.
rnk accepted this revision.Jan 23 2015, 3:50 PM
rnk added a reviewer: rnk.

lgtm

This revision is now accepted and ready to land.Jan 23 2015, 3:50 PM

Pleas use a test with one of the existing tools instead of a unit test.

In fact, you should be able to just add this to test/Other/ResponseFile.ll.

ygao closed this revision.Mar 18 2015, 6:25 PM