search for: setimm

Hi LLVM, IRBuilder can fold constants (that behaviour can be controlled by Folder type). What do you think about optionally allow IRBuilder to eliminate no-op instructions like `add %a, 0` or `memcpy(%a, %b, 0)`? - Paweł -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150423/4f99a092/attachment.html>

...quot; > #include "llvm/Support/CommandLine.h" > +#include "llvm/Target/TargetAsmInfo.h" > using namespace llvm; > > extern cl::opt<bool> EnablePPC32RS; // FIXME (64-bit): See > PPCRegisterInfo.cpp. > @@ -724,3 +725,21 @@ > > Cond > [0].setImm(PPC::InvertPredicate((PPC::Predicate)Cond[0].getImm())); > return false; > } > + > +/// GetInstSize - Return the number of bytes of code the specified > +/// instruction may be. This returns the maximum number of bytes. > +/// > +unsigned PPCInstrInfo::GetInstSize(const Mach...

OK, here's a new patch that adds the infrastructure and the implementation for X86, ARM and PPC of GetInstSize and GetFunctionSize. Both functions are virtual functions defined in TargetInstrInfo.h. For X86, I moved some commodity functions from X86CodeEmitter to X86InstrInfo. What do you think? Nicolas Evan Cheng wrote: > > I think both of these belong to TargetInstrInfo. And

...case Hexagon::JMP_GTUrrdnPt_ie_nv_V4: >> + case Hexagon::JMP_GTUrrdnPnt_ie_nv_V4: >> + case Hexagon::JMP_GTUrrdnNotPt_ie_nv_V4: >> + case Hexagon::JMP_GTUrrdnNotPnt_ie_nv_V4: >> + >> + // V4 absolute set addressing. >> + case Hexagon::LDrid_abs_setimm_V4: >> + case Hexagon::LDriw_abs_setimm_V4: >> + case Hexagon::LDrih_abs_setimm_V4: >> + case Hexagon::LDrib_abs_setimm_V4: >> + case Hexagon::LDriuh_abs_setimm_V4: >> + case Hexagon::LDriub_abs_setimm_V4: >> + >> + case Hexagon::STrid_abs...