Displaying 3 results from an estimated 3 matches for "isimmediate".
2017 Aug 23
1
[Bug 102382] New: nv50ir: isImmediate doesn't properly work for integers if Value is typed as float
https://bugs.freedesktop.org/show_bug.cgi?id=102382
Bug ID: 102382
Summary: nv50ir: isImmediate doesn't properly work for integers
if Value is typed as float
Product: xorg
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau...
2008 Apr 16
0
[LLVMdev] Being able to know the jitted code-size before emitting
...>
> BlockSizes[MBB->getNumber()] = BlockSize;
> FuncSize += BlockSize;
> @@ -124,7 +104,7 @@
> for (MachineBasicBlock::iterator I = MBB.begin(), E = MBB.end();
> I != E; ++I) {
> if (I->getOpcode() != PPC::BCC || I-
> >getOperand(2).isImmediate()) {
> - MBBStartOffset += getNumBytesForInstruction(I);
> + MBBStartOffset += TII->GetInstSize(I);
> continue;
> }
>
> Index: lib/Target/PowerPC/PPCInstrInfo.h
> ===================================================================
> ---...
2008 Apr 15
4
[LLVMdev] Being able to know the jitted code-size before emitting
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