llvm-project

Commit Graph

Author	SHA1	Message	Date
Richard Smith	ae500e4d09	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.	2020-08-16 15:44:51 -07:00
Richard Smith	9860e68450	Don't leave the FPOptions in a UnaryOperator uninitialized. We don't appear to use these FPOptions for anything right now, but they shouldn't be uninitialized because that makes our AST file output nondeterministic.	2020-08-16 15:16:12 -07:00

Author

SHA1

Message

Date

Richard Smith

ae500e4d09

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.

2020-08-16 15:44:51 -07:00

Richard Smith

9860e68450

Don't leave the FPOptions in a UnaryOperator uninitialized.

We don't appear to use these FPOptions for anything right now, but
they shouldn't be uninitialized because that makes our AST file output
nondeterministic.

2020-08-16 15:16:12 -07:00

2 Commits