Displaying 12 results from an estimated 12 matches for "newopcod".
Did you mean:
newopcode
2015 Mar 18
2
[LLVMdev] string input for the integrated assembler
On Tue, Mar 17, 2015 at 6:14 PM, Tim Northover <t.p.northover at gmail.com> wrote:
>> As a simplification, the compiler deals almost exclusively in pseudo
>> instructions. By x86 analogy, using pseudos to unfold a TEST32rm into
>> MOV32rm + TEST32rr means I can skip the complex operand fitting effort
>> needed to pick specific machine instructions. There are many
2012 Jan 24
2
[LLVMdev] Resolving branch instr with label "$BB0_-1"
Hi Aries.
Thanks very much!
Precisely this is the situation! There're two consecutive branches (br1cond and br2uncond). Inside of AnalyzeBranch, there's an opcode swap of br2uncond (ex. j_foward to j_backward). There I do BuildMI (newOpcode) and followed by br2uncond->eraseFromParent(). This results in br1cond loosing it's label/offset. How could I resolve this?
Best regards,
Girish.
May be you have branched to a BB which has been deleted.
>
>
>On 24 January 2012 20:16, girish gulawani <girishvg at yahoo.com>...
2013 Feb 14
0
[LLVMdev] changing opcode
...hanging opcode
>
> Is there a simple way to just change the opcode of a machine
> instruction.
>
> I have a lot of long/short pairs where when I know the offset, i can
> replace the long version with the short version.
Are you looking for something like this:
MI.setDesc(TII.get(NewOpcode));
This is in PPCRegisterInfo::eliminateFrameIndex.
-Hal
>
> Tia.
>
> REed
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmd...
2013 Feb 14
5
[LLVMdev] changing opcode
Is there a simple way to just change the opcode of a machine instruction.
I have a lot of long/short pairs where when I know the offset, i can
replace the long version with the short version.
Tia.
REed
2017 Dec 15
2
InstAlias with tied operands - can it be supported?
...39; can never be matched!");
// FIXME: Should reject these. The ARM backend hits this with
$lane in a
// bunch of instructions. It is unclear what the right answer is.
…
Is there a way to fix this limitation?
I would like to express: InstAlias<(opcode $rd, $rd, $rs1), (newopcode
$rd, $rs1)>
Thank you,
Ana.
--
Ana Pazos
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
2012 Jan 24
0
[LLVMdev] Resolving branch instr with label "$BB0_-1"
> Precisely this is the situation! There're two consecutive branches (br1cond
> and br2uncond). Inside of AnalyzeBranch, there's an opcode swap of br2uncond
> (ex. j_foward to j_backward). There I do BuildMI (newOpcode) and followed by
> br2uncond->eraseFromParent(). This results in br1cond loosing it's
> label/offset. How could I resolve this?
Your code is broken. AnalyzeBranch should not modify anything.
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersb...
2017 Dec 15
0
InstAlias with tied operands - can it be supported?
...ot;);
> // FIXME: Should reject these. The ARM backend hits this with $lane in a
> // bunch of instructions. It is unclear what the right answer is.
> …
>
> Is there a way to fix this limitation?
>
> I would like to express: InstAlias<(opcode $rd, $rd, $rs1), (newopcode $rd, $rs1)>
>
> Thank you,
> Ana.
>
>
> --
> Ana Pazos
> Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project.
> _______________________________________________
>...
2012 Jan 24
2
[LLVMdev] Resolving branch instr with label "$BB0_-1"
Hello All.
On a particular target the back-end generates an instruction like:
beqz r2, "$BB0_-1"
Is it a back-end specific issue? Could someone please help me figure out how this gets resolved? What confuses me is, all other branches are correctly labelled and resolved!
Thanks.
Girish.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2012 Jan 24
0
[LLVMdev] Resolving branch instr with label "$BB0_-1"
May be you have branched to a BB which has been deleted.
On 24 January 2012 20:16, girish gulawani <girishvg at yahoo.com> wrote:
>
> Hello All.
> On a particular target the back-end generates an instruction like:
> beqz r2, "$BB0_-1"
>
> Is it a back-end specific issue? Could someone please help me figure out
> how this gets resolved? What confuses me
2012 Jan 24
2
[LLVMdev] Resolving branch instr with label "$BB0_-1"
Hello Anton.
Thanks for the comment.
> Precisely this is the situation! There're two consecutive branches (br1cond
>> and br2uncond). Inside of AnalyzeBranch, there's an opcode swap of br2uncond
>> (ex. j_foward to j_backward). There I do BuildMI (newOpcode) and followed by
>> br2uncond->eraseFromParent(). This results in br1cond loosing it's
>> label/offset. How could I resolve this?
>Your code is broken. AnalyzeBranch should not modify anything.
>
>
>
>I was taking a clue from Mips/MipsInstrInfo.cpp: AnalyzeBranch...
2018 Jan 04
1
InstAlias with tied operands - can it be supported?
...e. The ARM backend hits this with
>> $lane in a
>> // bunch of instructions. It is unclear what the right answer
>> is.
>> …
>>
>> Is there a way to fix this limitation?
>>
>> I would like to express: InstAlias<(opcode $rd, $rd, $rs1), (newopcode
>> $rd, $rs1)>
>>
>> Thank you,
>> Ana.
>>
>>
>> --
>> Ana Pazos
>> Qualcomm Innovation Center, Inc.
>> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>> a Linux Foundation Collaborative Project.
>>...
2012 Apr 19
0
[LLVMdev] Target Dependent Hexagon Packetizer patch
...SDep::Kind DepType, MachineBasicBlock::iterator&MII,
>> + const TargetRegisterClass* RC) {
>> +
>> + assert (DepType == SDep::Data);
>> + const HexagonInstrInfo *QII = (const HexagonInstrInfo *) TII;
>> +
>> + int NewOpcode;
>> + if (RC == Hexagon::PredRegsRegisterClass)
>> + NewOpcode = GetDotNewPredOp(MI->getOpcode());
>> + else
>> + NewOpcode = GetDotNewOp(MI->getOpcode());
>> + MI->setDesc(QII->get(NewOpcode));
>> +
>> + return true;
>> +}
>...