summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/MultiplexConsumer.cpp
diff options
context:
space:
mode:
authorAlex Lorenz <arphaman@gmail.com>2015-06-18 20:57:41 +0000
committerAlex Lorenz <arphaman@gmail.com>2015-06-18 20:57:41 +0000
commit064441c02ac130d4e5d691b0ba43da19cbaeb149 (patch)
tree2e58d8ff0a67c96082a9dbc6fcccd745e51020f2 /clang/lib/Frontend/MultiplexConsumer.cpp
parentaaaa575f713a18b1aa19f4673bfddef00e40ff40 (diff)
downloadbcm5719-llvm-064441c02ac130d4e5d691b0ba43da19cbaeb149.tar.gz
bcm5719-llvm-064441c02ac130d4e5d691b0ba43da19cbaeb149.zip
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. llvm-svn: 240054
Diffstat (limited to 'clang/lib/Frontend/MultiplexConsumer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud