Displaying 1 result from an estimated 1 matches for "v6_zld0".
Did you mean:
v6_ld0
2020 Jan 14
3
[tablegen] table readability / performance
...without huge effort. The above table is now:
extern const char HexagonInstrNameData[] = {
/* 0 */ "G_FLOG10\0"
/* 9 */ "ENDLOOP0\0"
/* 18 */ "V6_vdd0\0"
/* 26 */ "PS_vdd0\0"
/* 34 */ "V6_ld0\0"
/* 41 */ "V6_zld0\0"
[...]
};
My question then is: Is there a specific technical reason that we should
avoid emitting concatenated string literals rather array of
comma-separated char literals for "string-like" data?
If not, I can probably post a patch, which I feel will make it much
easie...