Alex Lorenz 5f0fc6da46 MIR Serialization: initialize the fields without the default initializers in yaml::MachineFunction ... My commit r239790 which introduced serialization for simple machine function attributes didn't initialize them when parsing because I have misread the documentation for YAML IO's mapOptional method. The mapOptional method doesn't actually set the values to the values returned by the default constructor for that type when the key value pair is missing, it just doesn't modify those values, so they still contain the value that was set during initialization by the default constructor. But the fields in yaml::MachineFunction with types like unsigned and bool are not initialized by default, and thus they can still be uninitialized after mapOptional during parsing. This commit adds default initialization for those fields to prevent this. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@240054 91177308-0d34-0410-b5e6-96231b3b80d8		2015-06-18 20:57:41 +00:00
..
llvm	MIR Serialization: initialize the fields without the default initializers in yaml::MachineFunction	2015-06-18 20:57:41 +00:00
llvm-c	Update LLVM bindings after r239940. Apparently these aren't included in	2015-06-18 11:51:16 +00:00