diff options
author | Rui Ueyama <ruiu@google.com> | 2013-09-23 23:51:31 +0000 |
---|---|---|
committer | Rui Ueyama <ruiu@google.com> | 2013-09-23 23:51:31 +0000 |
commit | 456740c74031e7147a52df8e829b170df4aad29a (patch) | |
tree | 64fd458904de34b71f1255b1bb63fc043359a3f6 /clang/lib/Frontend/CompilerInvocation.cpp | |
parent | 1a73b8f7d2a2c4a8291039909a3108fb1d456c65 (diff) | |
download | bcm5719-llvm-456740c74031e7147a52df8e829b170df4aad29a.tar.gz bcm5719-llvm-456740c74031e7147a52df8e829b170df4aad29a.zip |
[PECOFF] Do not allow space to separate command line option and its value.
We used to support both Windows and Unix style command line options. In Windows
style, an option and its value are separated by ":" (colon). In Unix, separator
is a space. Accepting both styles were convenient, but we can no longer allow
Unix style because I found that can be ambiguous.
For example, /nodefaultlib option takes an optional argument. In Windows style
it's going to be something like "/nodefaultlib:foo". There's no ambiguity what
"foo" means. However, if the option is "/nodefaultlib foo", "foo" can be
interpreted either an optional argument for "/nodefaultlib" or an input file
"foo.obj". We should just stop accepting the non-standard command line style.
llvm-svn: 191247
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions