Add tricore tc1.8 instructions

[Changqing-JING]

Your checklist for this pull request

• I've documented or updated the documentation of every API function and struct this PR changes.
• I've added tests that prove my fix is effective or that my feature works (if possible)

Detailed description

Add tricore tc1.8 instructions:

add.df
sub.df
madd.df
msub.df
mul.df
div.df
cmp.df
max.df
min.df
min.f
max.f
dftoi
dftoiz
dftoin
ftoin
dftou
dftouz
dftol
dftoul
dftoulz
abs.f
abs.df
dftolz
neg.df
neg.f
qseed.df
itodf
utodf
ltodf
ultodf
dftof
ftodf
div64
div64.u
rem64
rem64.u

The inc files are updated by:
capstone-engine/llvm-capstone#73

...

Test plan

cmake --build ./build/linux-x64 && ./build/linux-x64/suite/cstest/Debug/cstest tests/MC/TriCore > build/test.lo

...

Closing issues

...

[XVilka]

@imbillow and this one, please

cc @Rot127

[Changqing-JING]

Since this PR is not merged yet. I added a bit more instructions

div64
div64.u
rem64
rem64.u

[Rot127]

I'll try to find time for a full review on the weekend. But please don't forget to add tests for the instruction details in tests/details.

[Changqing-JING]

@Rot127 Thank you very much for review.
I have added tests to tests/details

But I still have a question. The tests under tests/details seems similar to tests/MC. What's the reason to have both? Why not merge them to one?

[Rot127]

But I still have a question. The tests under tests/details seems similar to tests/MC. What's the reason to have both? Why not merge them to one?

The MC tests are copies of the assembler/disassembler regression tests from LLVM. They get translated from the LLVM format to our yaml test files with the Auto-Sync.
They effectively test all code which is from LLVM. And only the asm text. Not any of the details.

The detail tests on the other hand, test the code added by Capstone. So all the details. They should (but don't, yet) cover all functions in <ARCH>Mapping.c files.

[Rot127]

Lovely! Thanks a lot!
Just address those small comments please. Otherwise lgtm.
@kabeor