2012-02-18 20:03:15 +08:00
|
|
|
//===-- SparcInstrFormats.td - Sparc Instruction Formats ---*- tablegen -*-===//
|
|
|
|
//
|
2019-01-19 16:50:56 +08:00
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
2012-02-18 20:03:15 +08:00
|
|
|
//
|
2006-02-05 13:50:24 +08:00
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class InstSP<dag outs, dag ins, string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: Instruction {
|
2006-02-05 13:50:24 +08:00
|
|
|
field bits<32> Inst;
|
|
|
|
|
|
|
|
let Namespace = "SP";
|
2014-01-06 16:08:58 +08:00
|
|
|
let Size = 4;
|
2006-02-05 13:50:24 +08:00
|
|
|
|
|
|
|
bits<2> op;
|
|
|
|
let Inst{31-30} = op; // Top two bits are the 'op' field
|
2013-06-05 02:33:25 +08:00
|
|
|
|
Change instruction description to split OperandList into OutOperandList and
InOperandList. This gives one piece of important information: # of results
produced by an instruction.
An example of the change:
def ADD32rr : I<0x01, MRMDestReg, (ops GR32:$dst, GR32:$src1, GR32:$src2),
"add{l} {$src2, $dst|$dst, $src2}",
[(set GR32:$dst, (add GR32:$src1, GR32:$src2))]>;
=>
def ADD32rr : I<0x01, MRMDestReg, (outs GR32:$dst), (ins GR32:$src1, GR32:$src2),
"add{l} {$src2, $dst|$dst, $src2}",
[(set GR32:$dst, (add GR32:$src1, GR32:$src2))]>;
llvm-svn: 40033
2007-07-19 09:14:50 +08:00
|
|
|
dag OutOperandList = outs;
|
|
|
|
dag InOperandList = ins;
|
2006-02-05 13:50:24 +08:00
|
|
|
let AsmString = asmstr;
|
|
|
|
let Pattern = pattern;
|
2014-01-06 16:08:58 +08:00
|
|
|
|
|
|
|
let DecoderNamespace = "Sparc";
|
|
|
|
field bits<32> SoftFail = 0;
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
|
|
|
|
let Itinerary = itin;
|
2006-02-05 13:50:24 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
// Format #2 instruction classes in the Sparc
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
// Format 2 instructions
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class F2<dag outs, dag ins, string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: InstSP<outs, ins, asmstr, pattern, itin> {
|
2006-02-05 13:50:24 +08:00
|
|
|
bits<3> op2;
|
|
|
|
bits<22> imm22;
|
|
|
|
let op = 0; // op = 0
|
|
|
|
let Inst{24-22} = op2;
|
|
|
|
let Inst{21-0} = imm22;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Specific F2 classes: SparcV8 manual, page 44
|
|
|
|
//
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class F2_1<bits<3> op2Val, dag outs, dag ins, string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: F2<outs, ins, asmstr, pattern, itin> {
|
2006-02-05 13:50:24 +08:00
|
|
|
bits<5> rd;
|
|
|
|
|
|
|
|
let op2 = op2Val;
|
|
|
|
|
|
|
|
let Inst{29-25} = rd;
|
|
|
|
}
|
|
|
|
|
2014-03-02 04:08:48 +08:00
|
|
|
class F2_2<bits<3> op2Val, bit annul, dag outs, dag ins, string asmstr,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
list<dag> pattern, InstrItinClass itin = NoItinerary>
|
|
|
|
: F2<outs, ins, asmstr, pattern, itin> {
|
2006-02-05 13:50:24 +08:00
|
|
|
bits<4> cond;
|
|
|
|
let op2 = op2Val;
|
|
|
|
|
|
|
|
let Inst{29} = annul;
|
|
|
|
let Inst{28-25} = cond;
|
|
|
|
}
|
|
|
|
|
2014-03-02 06:03:07 +08:00
|
|
|
class F2_3<bits<3> op2Val, bit annul, bit pred,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
dag outs, dag ins, string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: InstSP<outs, ins, asmstr, pattern, itin> {
|
2014-03-02 06:03:07 +08:00
|
|
|
bits<2> cc;
|
2014-01-06 16:08:58 +08:00
|
|
|
bits<4> cond;
|
|
|
|
bits<19> imm19;
|
|
|
|
|
|
|
|
let op = 0; // op = 0
|
|
|
|
|
|
|
|
let Inst{29} = annul;
|
|
|
|
let Inst{28-25} = cond;
|
|
|
|
let Inst{24-22} = op2Val;
|
2014-03-02 06:03:07 +08:00
|
|
|
let Inst{21-20} = cc;
|
2014-01-06 16:08:58 +08:00
|
|
|
let Inst{19} = pred;
|
|
|
|
let Inst{18-0} = imm19;
|
|
|
|
}
|
|
|
|
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class F2_4<bits<3> cond, bit annul, bit pred, dag outs, dag ins,
|
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = NoItinerary>
|
|
|
|
: InstSP<outs, ins, asmstr, pattern, itin> {
|
2014-03-02 17:46:56 +08:00
|
|
|
bits<16> imm16;
|
|
|
|
bits<5> rs1;
|
|
|
|
|
|
|
|
let op = 0; // op = 0
|
|
|
|
|
|
|
|
let Inst{29} = annul;
|
|
|
|
let Inst{28} = 0;
|
|
|
|
let Inst{27-25} = cond;
|
|
|
|
let Inst{24-22} = 0b011;
|
|
|
|
let Inst{21-20} = imm16{15-14};
|
|
|
|
let Inst{19} = pred;
|
|
|
|
let Inst{18-14} = rs1;
|
|
|
|
let Inst{13-0} = imm16{13-0};
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2006-02-05 13:50:24 +08:00
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
// Format #3 instruction classes in the Sparc
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class F3<dag outs, dag ins, string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: InstSP<outs, ins, asmstr, pattern, itin> {
|
2006-02-05 13:50:24 +08:00
|
|
|
bits<5> rd;
|
|
|
|
bits<6> op3;
|
|
|
|
bits<5> rs1;
|
|
|
|
let op{1} = 1; // Op = 2 or 3
|
|
|
|
let Inst{29-25} = rd;
|
|
|
|
let Inst{24-19} = op3;
|
|
|
|
let Inst{18-14} = rs1;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Specific F3 classes: SparcV8 manual, page 44
|
|
|
|
//
|
Sparc: Add the "alternate address space" load/store instructions.
- Adds support for the asm syntax, which has an immediate integer
"ASI" (address space identifier) appearing after an address, before
a comma.
- Adds the various-width load, store, and swap in alternate address
space instructions. (ldsba, ldsha, lduba, lduha, lda, stba, stha,
sta, swapa)
This does not attempt to hook these instructions up to pointer address
spaces in LLVM, although that would probably be a reasonable thing to
do in the future.
Differential Revision: http://reviews.llvm.org/D8904
llvm-svn: 237581
2015-05-19 00:35:04 +08:00
|
|
|
class F3_1_asi<bits<2> opVal, bits<6> op3val, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = NoItinerary>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
Sparc: Add the "alternate address space" load/store instructions.
- Adds support for the asm syntax, which has an immediate integer
"ASI" (address space identifier) appearing after an address, before
a comma.
- Adds the various-width load, store, and swap in alternate address
space instructions. (ldsba, ldsha, lduba, lduha, lda, stba, stha,
sta, swapa)
This does not attempt to hook these instructions up to pointer address
spaces in LLVM, although that would probably be a reasonable thing to
do in the future.
Differential Revision: http://reviews.llvm.org/D8904
llvm-svn: 237581
2015-05-19 00:35:04 +08:00
|
|
|
bits<8> asi;
|
2006-02-05 13:50:24 +08:00
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let op = opVal;
|
|
|
|
let op3 = op3val;
|
|
|
|
|
|
|
|
let Inst{13} = 0; // i field = 0
|
|
|
|
let Inst{12-5} = asi; // address space identifier
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
|
|
|
|
2014-02-07 15:34:49 +08:00
|
|
|
class F3_1<bits<2> opVal, bits<6> op3val, dag outs, dag ins, string asmstr,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
list<dag> pattern, InstrItinClass itin = IIC_iu_instr>
|
|
|
|
: F3_1_asi<opVal, op3val, outs, ins, asmstr, pattern, itin> {
|
Sparc: Add the "alternate address space" load/store instructions.
- Adds support for the asm syntax, which has an immediate integer
"ASI" (address space identifier) appearing after an address, before
a comma.
- Adds the various-width load, store, and swap in alternate address
space instructions. (ldsba, ldsha, lduba, lduha, lda, stba, stha,
sta, swapa)
This does not attempt to hook these instructions up to pointer address
spaces in LLVM, although that would probably be a reasonable thing to
do in the future.
Differential Revision: http://reviews.llvm.org/D8904
llvm-svn: 237581
2015-05-19 00:35:04 +08:00
|
|
|
let asi = 0;
|
|
|
|
}
|
2014-02-07 15:34:49 +08:00
|
|
|
|
2013-06-05 02:33:25 +08:00
|
|
|
class F3_2<bits<2> opVal, bits<6> op3val, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = IIC_iu_instr>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
2006-02-05 13:50:24 +08:00
|
|
|
bits<13> simm13;
|
|
|
|
|
|
|
|
let op = opVal;
|
|
|
|
let op3 = op3val;
|
|
|
|
|
|
|
|
let Inst{13} = 1; // i field = 1
|
|
|
|
let Inst{12-0} = simm13;
|
|
|
|
}
|
|
|
|
|
|
|
|
// floating-point
|
Change instruction description to split OperandList into OutOperandList and
InOperandList. This gives one piece of important information: # of results
produced by an instruction.
An example of the change:
def ADD32rr : I<0x01, MRMDestReg, (ops GR32:$dst, GR32:$src1, GR32:$src2),
"add{l} {$src2, $dst|$dst, $src2}",
[(set GR32:$dst, (add GR32:$src1, GR32:$src2))]>;
=>
def ADD32rr : I<0x01, MRMDestReg, (outs GR32:$dst), (ins GR32:$src1, GR32:$src2),
"add{l} {$src2, $dst|$dst, $src2}",
[(set GR32:$dst, (add GR32:$src1, GR32:$src2))]>;
llvm-svn: 40033
2007-07-19 09:14:50 +08:00
|
|
|
class F3_3<bits<2> opVal, bits<6> op3val, bits<9> opfval, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = NoItinerary>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
2006-02-05 13:50:24 +08:00
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let op = opVal;
|
|
|
|
let op3 = op3val;
|
|
|
|
|
|
|
|
let Inst{13-5} = opfval; // fp opcode
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
2006-09-02 06:28:02 +08:00
|
|
|
|
2013-09-22 17:54:42 +08:00
|
|
|
// floating-point unary operations.
|
|
|
|
class F3_3u<bits<2> opVal, bits<6> op3val, bits<9> opfval, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = NoItinerary>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
2013-09-22 17:54:42 +08:00
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let op = opVal;
|
|
|
|
let op3 = op3val;
|
|
|
|
let rs1 = 0;
|
|
|
|
|
|
|
|
let Inst{13-5} = opfval; // fp opcode
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
|
|
|
|
|
|
|
// floating-point compares.
|
|
|
|
class F3_3c<bits<2> opVal, bits<6> op3val, bits<9> opfval, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = NoItinerary>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
2013-09-22 17:54:42 +08:00
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let op = opVal;
|
|
|
|
let op3 = op3val;
|
|
|
|
|
|
|
|
let Inst{13-5} = opfval; // fp opcode
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
|
|
|
|
2013-04-02 12:09:12 +08:00
|
|
|
// Shift by register rs2.
|
|
|
|
class F3_Sr<bits<2> opVal, bits<6> op3val, bit xVal, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = IIC_iu_instr>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
2013-04-02 12:09:12 +08:00
|
|
|
bit x = xVal; // 1 for 64-bit shifts.
|
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let op = opVal;
|
|
|
|
let op3 = op3val;
|
|
|
|
|
|
|
|
let Inst{13} = 0; // i field = 0
|
|
|
|
let Inst{12} = x; // extended registers.
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
2006-09-02 06:28:02 +08:00
|
|
|
|
2013-04-02 12:09:12 +08:00
|
|
|
// Shift by immediate.
|
|
|
|
class F3_Si<bits<2> opVal, bits<6> op3val, bit xVal, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern, InstrItinClass itin = IIC_iu_instr>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
2013-04-02 12:09:12 +08:00
|
|
|
bit x = xVal; // 1 for 64-bit shifts.
|
|
|
|
bits<6> shcnt; // shcnt32 / shcnt64.
|
|
|
|
|
|
|
|
let op = opVal;
|
|
|
|
let op3 = op3val;
|
|
|
|
|
|
|
|
let Inst{13} = 1; // i field = 1
|
|
|
|
let Inst{12} = x; // extended registers.
|
|
|
|
let Inst{5-0} = shcnt;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Define rr and ri shift instructions with patterns.
|
|
|
|
multiclass F3_S<string OpcStr, bits<6> Op3Val, bit XVal, SDNode OpNode,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
ValueType VT, RegisterClass RC,
|
|
|
|
InstrItinClass itin = IIC_iu_instr> {
|
2014-01-08 15:47:57 +08:00
|
|
|
def rr : F3_Sr<2, Op3Val, XVal, (outs RC:$rd), (ins RC:$rs1, IntRegs:$rs2),
|
|
|
|
!strconcat(OpcStr, " $rs1, $rs2, $rd"),
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
[(set VT:$rd, (OpNode VT:$rs1, i32:$rs2))],
|
|
|
|
itin>;
|
2014-01-08 15:47:57 +08:00
|
|
|
def ri : F3_Si<2, Op3Val, XVal, (outs RC:$rd), (ins RC:$rs1, i32imm:$shcnt),
|
|
|
|
!strconcat(OpcStr, " $rs1, $shcnt, $rd"),
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
[(set VT:$rd, (OpNode VT:$rs1, (i32 imm:$shcnt)))],
|
|
|
|
itin>;
|
2013-04-02 12:09:12 +08:00
|
|
|
}
|
2013-09-22 17:18:26 +08:00
|
|
|
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class F4<bits<6> op3, dag outs, dag ins, string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: InstSP<outs, ins, asmstr, pattern, itin> {
|
2013-09-22 17:18:26 +08:00
|
|
|
bits<5> rd;
|
|
|
|
|
|
|
|
let op = 2;
|
|
|
|
let Inst{29-25} = rd;
|
|
|
|
let Inst{24-19} = op3;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
class F4_1<bits<6> op3, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: F4<op3, outs, ins, asmstr, pattern, itin> {
|
2014-03-02 12:43:45 +08:00
|
|
|
bit intcc;
|
|
|
|
bits<2> cc;
|
2013-09-22 17:18:26 +08:00
|
|
|
bits<4> cond;
|
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let Inst{4-0} = rs2;
|
2014-03-02 12:43:45 +08:00
|
|
|
let Inst{12-11} = cc;
|
2013-09-22 17:18:26 +08:00
|
|
|
let Inst{13} = 0;
|
|
|
|
let Inst{17-14} = cond;
|
2014-03-02 12:43:45 +08:00
|
|
|
let Inst{18} = intcc;
|
2013-09-22 17:18:26 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
class F4_2<bits<6> op3, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: F4<op3, outs, ins, asmstr, pattern, itin> {
|
2014-03-02 12:43:45 +08:00
|
|
|
bit intcc;
|
|
|
|
bits<2> cc;
|
2013-09-22 17:18:26 +08:00
|
|
|
bits<4> cond;
|
|
|
|
bits<11> simm11;
|
|
|
|
|
|
|
|
let Inst{10-0} = simm11;
|
2014-03-02 12:43:45 +08:00
|
|
|
let Inst{12-11} = cc;
|
2013-09-22 17:18:26 +08:00
|
|
|
let Inst{13} = 1;
|
|
|
|
let Inst{17-14} = cond;
|
2014-03-02 12:43:45 +08:00
|
|
|
let Inst{18} = intcc;
|
2013-09-22 17:18:26 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
class F4_3<bits<6> op3, bits<6> opf_low, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: F4<op3, outs, ins, asmstr, pattern, itin> {
|
2013-09-22 17:18:26 +08:00
|
|
|
bits<4> cond;
|
2014-03-02 12:43:45 +08:00
|
|
|
bit intcc;
|
|
|
|
bits<2> opf_cc;
|
2013-09-22 17:18:26 +08:00
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let Inst{18} = 0;
|
|
|
|
let Inst{17-14} = cond;
|
2014-03-02 12:43:45 +08:00
|
|
|
let Inst{13} = intcc;
|
|
|
|
let Inst{12-11} = opf_cc;
|
2013-09-22 17:18:26 +08:00
|
|
|
let Inst{10-5} = opf_low;
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
2014-03-02 17:46:56 +08:00
|
|
|
|
|
|
|
class F4_4r<bits<6> op3, bits<5> opf_low, bits<3> rcond, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: F4<op3, outs, ins, asmstr, pattern, itin> {
|
2014-03-02 17:46:56 +08:00
|
|
|
bits <5> rs1;
|
|
|
|
bits <5> rs2;
|
|
|
|
let Inst{18-14} = rs1;
|
|
|
|
let Inst{13} = 0; // IsImm
|
|
|
|
let Inst{12-10} = rcond;
|
|
|
|
let Inst{9-5} = opf_low;
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
class F4_4i<bits<6> op3, bits<3> rcond, dag outs, dag ins,
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: F4<op3, outs, ins, asmstr, pattern, itin> {
|
2014-03-02 17:46:56 +08:00
|
|
|
bits<5> rs1;
|
|
|
|
bits<10> simm10;
|
|
|
|
let Inst{18-14} = rs1;
|
|
|
|
let Inst{13} = 1; // IsImm
|
|
|
|
let Inst{12-10} = rcond;
|
|
|
|
let Inst{9-0} = simm10;
|
|
|
|
}
|
2014-03-03 07:39:07 +08:00
|
|
|
|
|
|
|
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class TRAPSP<bits<6> op3Val, bit isimm, dag outs, dag ins,
|
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: F3<outs, ins, asmstr, pattern, itin> {
|
2014-03-03 07:39:07 +08:00
|
|
|
bits<4> cond;
|
|
|
|
bits<2> cc;
|
|
|
|
|
|
|
|
let op = 0b10;
|
|
|
|
let rd{4} = 0;
|
|
|
|
let rd{3-0} = cond;
|
|
|
|
let op3 = op3Val;
|
|
|
|
let Inst{13} = isimm;
|
|
|
|
let Inst{12-11} = cc;
|
|
|
|
|
|
|
|
}
|
|
|
|
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
class TRAPSPrr<bits<6> op3Val, dag outs, dag ins,
|
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: TRAPSP<op3Val, 0, outs, ins, asmstr, pattern, itin> {
|
2014-03-03 07:39:07 +08:00
|
|
|
bits<5> rs2;
|
|
|
|
|
|
|
|
let Inst{10-5} = 0;
|
|
|
|
let Inst{4-0} = rs2;
|
|
|
|
}
|
[Sparc] This provides support for itineraries on Sparc.
Specifically, itineraries for LEON processors has been added, along with several LEON processor Subtargets. Although currently all these targets are pretty much identical, support for features that will differ among these processors will be added in the very near future.
The different Instruction Itinerary Classes (IICs) added are sufficient to differentiate between the instruction timings used by LEON and, quite probably, by generic Sparc processors too, but the focus of the exercise has been for LEON processors, as the requirement of my project. If the IICs are not sufficient for other Sparc processor types and you want to add a new itinerary for one of those, it should be relatively trivial to adapt this.
As none of the LEON processors has Quad Floats, or is a Version 9 processor, none of those instructions have itinerary classes defined and revert to the default "NoItinerary" instruction itinerary.
Phabricator Review: http://reviews.llvm.org/D19359
llvm-svn: 267121
2016-04-22 16:17:17 +08:00
|
|
|
|
|
|
|
class TRAPSPri<bits<6> op3Val, dag outs, dag ins,
|
|
|
|
string asmstr, list<dag> pattern,
|
|
|
|
InstrItinClass itin = NoItinerary>
|
|
|
|
: TRAPSP<op3Val, 1, outs, ins, asmstr, pattern, itin> {
|
2014-03-03 07:39:07 +08:00
|
|
|
bits<8> imm;
|
|
|
|
|
|
|
|
let Inst{10-8} = 0;
|
|
|
|
let Inst{7-0} = imm;
|
|
|
|
}
|
2015-05-19 00:43:33 +08:00
|
|
|
|
|
|
|
// Pseudo-instructions for alternate assembly syntax (never used by codegen).
|
|
|
|
// These are aliases that require C++ handling to convert to the target
|
|
|
|
// instruction, while InstAliases can be handled directly by tblgen.
|
|
|
|
class AsmPseudoInst<dag outs, dag ins, string asm>
|
|
|
|
: InstSP<outs, ins, asm, []> {
|
|
|
|
let isPseudo = 1;
|
|
|
|
}
|