Always keep unset fields in FPOptionsOverride zeroed.
authorRichard Smith <richard@metafoo.co.uk>
Sun, 16 Aug 2020 22:44:51 +0000 (15:44 -0700)
committerRichard Smith <richard@metafoo.co.uk>
Sun, 16 Aug 2020 22:44:51 +0000 (15:44 -0700)
commitae500e4d0964adea69372d083416b0f13e9a87eb
tree969a335233779c5c2f295b74f1c20908ae7260d1
parentae3067055b33f6ab5657fbae5845cc743b91c299
Always keep unset fields in FPOptionsOverride zeroed.

There are three fields that the FPOptions default constructor sets to
non-zero values; those fields previously could have been zero or
non-zero depending on whether they'd been explicitly removed from the
FPOptionsOverride set. However, that doesn't seem to ever actually
happen, so this is NFC, except that it makes the AST file representation
of FPOptionsOverride make more sense.
clang/include/clang/Basic/LangOptions.h
clang/test/PCH/determinism.cpp