search for: createcodetoloadconst

...tand this logic. If we have "1 + 2" as constant expression, then why emit the code to perform addition? It should be possible to just fold the expression and copy immediate "3" into a register. I must be missing something, but what? Another question is about TargetInstrInfo::CreateCodeToLoadConst. This seems like a perfect fit for the task, but it's not used in X86 backend at all. Further, the destination register is represented by Instruction*, and not by integer number as elsewhere. What does that Instruction* mean? Thanks, Volodya

...X; int Y; int Z = (int)&X-(int)&Y; Yes, this is gross and disturbing, but we do support it. Constant expressions are the reason why there is a separation in the X86 isel between the "visit" methods and the "emit" methods. > Another question is about TargetInstrInfo::CreateCodeToLoadConst. This seems > like a perfect fit for the task, but it's not used in X86 backend at all. > Further, the destination register is represented by Instruction*, and not by > integer number as elsewhere. What does that Instruction* mean? This is a deprecated method that is only used by the...

...Yes, this is gross and disturbing, but we do support it. Constant > expressions are the reason why there is a separation in the X86 isel > between the "visit" methods and the "emit" methods. Thanks for the explanation? > > Another question is about TargetInstrInfo::CreateCodeToLoadConst. This > > seems like a perfect fit for the task, but it's not used in X86 backend > > at all. Further, the destination register is represented by Instruction*, > > and not by integer number as elsewhere. What does that Instruction* mean? > > This is a deprecated method t...