search for: addglobalvalu

...tion, MachineOperand is created with the char* argument, but the argument is not copied, it's just stored in MachineOperand::symbolName. So, all long as string temporary is destroyed, that pointer points to garbage. I suppose I could handle this by adding function to LLVM module and using .addGlobalValue, but still, is the non-copying behaviour of constructor by design? - Volodya

...; is created with the char* argument, but the argument is not copied, it's > just stored in MachineOperand::symbolName. So, all long as string > temporary is destroyed, that pointer points to garbage. I suppose I > could handle this by adding function to LLVM module and using > .addGlobalValue, but still, is the non-copying behaviour of constructor > by design? Yes, this is by design. MachineOperand is supposed to be a very light-weight union. We actually used to have it carry an std::string around, but this required conditional code to make sure to free it and copy it when ne...

...h the char* argument, but the argument is not copied, it's > > just stored in MachineOperand::symbolName. So, all long as string > > temporary is destroyed, that pointer points to garbage. I suppose I > > could handle this by adding function to LLVM module and using > > .addGlobalValue, but still, is the non-copying behaviour of constructor > > by design? > > Yes, this is by design. MachineOperand is supposed to be a very > light-weight union. We actually used to have it carry an std::string > around, but this required conditional code to make sure to free it...