llvm-project/clang/test/Driver/at_file.c.args.utf16le

<EFBFBD><EFBFBD>-Dfoo1=bar1 -Dfoo2="bar2 zed2"
-Dfoo3='bar3 zed3'
"-Dfoo4=bar4 zed4"
'-Dfoo5=bar5 zed5'
-Dfoo6="'bar6 zed6'"
-Dfoo7='"bar7 zed7"'
-Dfoo8=foo8"bar8"zed8
-Dfoo9=foo9\'bar9\'zed9
-Dfoo10=foo10\"bar10\"zed10
-D foo11
-Dfoo12=zed12\
-Dfoo13='one\\two'
-Dfoo14='c:\foo\bar.c'
-												[Driver] Use LLVM's response file parser because it can read UTF-16

MSBuild writes response files as UTF-16 little endian with a byte order
mark.  With this change, clang will be able to read them, although we
still can't parse any of their flags.

Adds a UTF-16-LE response file with a BOM for testing.

Differential Revision: http://llvm-reviews.chandlerc.com/D1137

llvm-svn: 186603

											
										
										
											2013-07-19 04:00:53 +08:00
+								<EFBFBD><EFBFBD>-Dfoo1=bar1 -Dfoo2="bar2 zed2"
 								-Dfoo3='bar3 zed3'
 								"-Dfoo4=bar4 zed4"
 								'-Dfoo5=bar5 zed5'
 								-Dfoo6="'bar6 zed6'"
 								-Dfoo7='"bar7 zed7"'
 								-Dfoo8=foo8"bar8"zed8
 								-Dfoo9=foo9\'bar9\'zed9
 								-Dfoo10=foo10\"bar10\"zed10
 								-D foo11
 								-Dfoo12=zed12\
 								-Dfoo13='one\\two'
-												Expand test/Driver/at_file.c test to check that PR16209 is fixed.

It was fixed by r186603.

llvm-svn: 186962

											
										
										
											2013-07-24 01:26:56 +08:00
+								-Dfoo14='c:\foo\bar.c'
-												[Driver] Use LLVM's response file parser because it can read UTF-16

MSBuild writes response files as UTF-16 little endian with a byte order
mark.  With this change, clang will be able to read them, although we
still can't parse any of their flags.

Adds a UTF-16-LE response file with a BOM for testing.

Differential Revision: http://llvm-reviews.chandlerc.com/D1137

llvm-svn: 186603

											
										
										
											2013-07-19 04:00:53 +08:00