search for: instrnamedata

Hello I've been looking at the tables generated by `SequenceToOffsetTable::emit`, and notice that when the generated data are strings, the data is basically un-grep-able, and very tricky to read, as they are emitted as an array of comma-separated char-literal: extern const char HexagonInstrNameData[] = { /* 0 */ 'G', '_', 'F', 'L', 'O', 'G', '1', '0', 0, /* 9 */ 'E', 'N', 'D', 'L', 'O', 'O', 'P', '0', 0, /* 18 */ 'V', '6', '_'...

Hello everyone! There is segmentation fault during translating a simple function with my backend. Investigation with gdb has shown that address of InstrNameData array in generated file MyTargetGenInstrInfo.inc is out of bounds. Also, if I run llc without -view-dag options, NumOpcodes equals 0 inside llvm::MCInstrInfo::get function, although there are some instructions (they are appeared in MyTargetGenInstrInfo.inc file). File MyTargetMCTargetDesc.cpp con...