search for: relhexagon

...ne string variable for each basic format required for relation modeling. All instructions that want to define relationship mapping, should inherit from this class in addition to RelationMap class. This is explained below using a prototype model for Hexagon. Example from Hexagon backend: class RelHexagon : Relations { string InstFormat0; //prev form string InstFormat1; //rr (register register) string InstFormat2; //ri (register immediate) string InstFormat3; //pred true string InstFormat4; //pred false } Define Instruction formats which are IFormat objects and have a unique integer value...

On Aug 1, 2012, at 1:53 PM, Jyotsna Verma <jverma at codeaurora.org> wrote: > > Currently, we rely on switch tables to transform between formats. However, > we would like to have a different mechanism to represent these relationships > instead of switch tables. I am thinking of modeling these relations in > HexagonInstrInfo.td file and use TableGen to generate a table with

Hi, I'm looking for some suggestions on a problem related to the Hexagon backend. Hexagon architecture allows instructions in various formats. For example, we have 3 variations of the add instruction as defined below: ADDrr : r1 = add(r2, r3) --> add 2 32-bit registers ADDrr_p : if(p0) r1 = add(r2, r3) --> predicated version of ADDrr instruction, executed when p0 is true ADDrr_np :

...Dtrue, ADDfalse, // BaseOpcode="ADD" { SUB , SUBtrue, SUBfalse, // BaseOpcode="SUB" … > 5) We need some changes in the TGParser.cpp so that it can use the > information specified > through the RelationMap and populate relevant fields in the RelHexagon > class. The tablegen parser is definitely not the right place to implement this. /jakob

...// BaseOpcode="ADD" > { SUB , SUBtrue, SUBfalse, // BaseOpcode="SUB" > > > 5) We need some changes in the TGParser.cpp so that it can use the > > information specified through the RelationMap and populate relevant > > fields in the RelHexagon class. > > The tablegen parser is definitely not the right place to implement this. I didn't want to modify the tablegen parser either. But, I couldn't think of a way around it. Once instructions are expended by the TableGen parser, there is no way to relate them. Since I wanted to...