diff options
| author | Jan Svoboda <jan_svoboda@apple.com> | 2021-01-26 08:27:40 +0100 |
|---|---|---|
| committer | Jan Svoboda <jan_svoboda@apple.com> | 2021-01-26 08:41:39 +0100 |
| commit | b61639985e216e75727f623174ec32a2a7cf40e3 (patch) | |
| tree | 8756a577dc2e25cd4024ad39822c16cdfdd6698a /clang/unittests/Frontend/CompilerInvocationTest.cpp | |
| parent | 90ebc489ded3eb7568c719e06916dd7945e30bec (diff) | |
| download | llvm-b61639985e216e75727f623174ec32a2a7cf40e3.zip llvm-b61639985e216e75727f623174ec32a2a7cf40e3.tar.gz llvm-b61639985e216e75727f623174ec32a2a7cf40e3.tar.bz2 | |
[clang][cli] NFC: Simplify BoolOption API
The `Bool{,F,G}Option` TableGen classes were designed after `Opt{In,Out}FFlag`, which put marshalling info on only one of the boolean options. To encode which record is supposed to carry the marshalling info (and be visible on -cc1 command-line), we used the `ChangedBy` and `ResetBy` classes.
However, we need to put marshalling info on both records anyways (see D93008 for details). This means we don't really need the distinction between `ChangedBy/ResetBy + BoolOption` and `FlagDef + BoolOptionBase` anymore.
This patch reduces the number of ways one can encode the marshalling information for pairs of boolean flags. Regardless of whether the key path value defaults to a statically known boolean, or a result of an expression, one can always use the new `BoolOption` and `PosFlag<SetTrue>, NegFlag<SetFalse>` syntax.
Reviewed By: dexonsmith
Differential Revision: https://reviews.llvm.org/D95340
Diffstat (limited to 'clang/unittests/Frontend/CompilerInvocationTest.cpp')
0 files changed, 0 insertions, 0 deletions