Nico Weber 1254b69520 Let unaliased Args track which Alias they were created from, and use that in Arg::getAsString() for diagnostics ... With this, `clang-cl /source-charset:utf-16 test.cc` now prints `invalid value 'utf-16' in '/source-charset:utf-16'` instead of `invalid value 'utf-16' in '-finput-charset=utf-16'` before, and several other clang-cl flags produce much less confusing output as well. Fixes PR29106. Since an arg and its alias can have different arg types (joined vs not) and different values (because of AliasArgs<>), I chose to give the Alias its own Arg object. For convenience, I just store the alias directly in the unaliased arg – there aren't many arg objects at runtime, so that seems ok. Finally, I changed Arg::getAsString() to use the alias's representation if it's present – that function was already documented as being the suitable function for diagnostics, and most callers already used it for diagnostics. Implementation-wise, Arg::accept() previously used to parse things as the unaliased option. The core of that switch is now extracted into a new function acceptInternal() which parses as the _aliased_ option, and the previously-intermingled unaliasing is now done as an explicit step afterwards. (This also changes one place in lld that didn't use getAsString() for diagnostics, so that that one place now also prints the flag as the user wrote it, not as it looks after it went through unaliasing.) Differential Revision: https://reviews.llvm.org/D64253 llvm-svn: 365413		2019-07-09 00:34:08 +00:00
..
Arg.cpp	Let unaliased Args track which Alias they were created from, and use that in Arg::getAsString() for diagnostics	2019-07-09 00:34:08 +00:00
ArgList.cpp
CMakeLists.txt
LLVMBuild.txt
Option.cpp	Let unaliased Args track which Alias they were created from, and use that in Arg::getAsString() for diagnostics	2019-07-09 00:34:08 +00:00
OptTable.cpp