search for: getpredicatedopcode

Displaying 5 results from an estimated 5 matches for "getpredicatedopcode".

2012 Aug 17
0
[LLVMdev] TableGen related question for the Hexagon backend
...instructions you want. You simply use the existing fields in your instructions, or add new ones as needed. You don't want to be limited to a single 'IFormat' as a column identifier, there can be many different types of relationships between instructions. Do something like this: def getPredicatedOpcode : InstrMapping { // Only include instructions form the PredRel class. let FilterClass = "PredRel"; // Instructions with the same BaseOpcode field form a row. let RowFields = ["BaseOpcode"]; // Instructions with the same predicate sense form a column. let ColFields...
2012 Aug 17
2
[LLVMdev] TableGen related question for the Hexagon backend
...ping table. def Format_rr : IFormat<1>; def Format_ri : IFormat<2>; def Format_predt : IFormat<3>; def Format_predf : IFormat<4>; Addrr : { Addrr, Addri, Addrr_pt, Addrr_pf, .. , ..} Addri : { Addrr, Addri, Addri_pt, Addri_pf,.. > Do something like this: > > def getPredicatedOpcode : InstrMapping { > // Only include instructions form the PredRel class. > let FilterClass = "PredRel"; > > // Instructions with the same BaseOpcode field form a row. > let RowFields = ["BaseOpcode"]; > > // Instructions with the same predicate se...
2012 Aug 17
0
[LLVMdev] TableGen related question for the Hexagon backend
...pe of relationships between instructions. I define > multiple IFormat objects one per relationship which finally translates into > a unique column into the mapping table. My point is that you don't need to define additional structure when you can just use the record fields. >> def getPredicatedOpcode : InstrMapping { >> // Only include instructions form the PredRel class. >> let FilterClass = "PredRel"; >> >> // Instructions with the same BaseOpcode field form a row. >> let RowFields = ["BaseOpcode"]; >> >> // Instructions wit...
2012 Aug 16
2
[LLVMdev] TableGen related question for the Hexagon backend
Hi Everyone, After some more thoughts to the Jacob's suggestion of using multiclasses for Opcode mapping, this is what I have come up with. Please take a look at the design below and let me know if you have any suggestions/questions. I have tried to keep the design target independent so that other targets could benefit from it. 1) The idea is to add 3 new classes into
2012 Aug 20
2
[LLVMdev] TableGen related question for the Hexagon backend
...tions. I > > define multiple IFormat objects one per relationship which finally > > translates into a unique column into the mapping table. > > My point is that you don't need to define additional structure when you can > just use the record fields. > > >> def getPredicatedOpcode : InstrMapping { // Only include > >> instructions form the PredRel class. > >> let FilterClass = "PredRel"; > >> > >> // Instructions with the same BaseOpcode field form a row. > >> let RowFields = ["BaseOpcode"]; > >> &...