User Details
- User Since
- Jun 7 2017, 5:05 AM (302 w, 4 d)
Feb 19 2020
Feb 18 2020
Reverted in rG7603bfb4b0a6.
Ping.
Feb 10 2020
Feb 7 2020
Formatted patch.
Feb 6 2020
Feb 5 2020
Jan 28 2020
Jan 27 2020
Jan 23 2020
Jan 22 2020
Jan 21 2020
Initial MIPS support was also added to llvm-exegesis.
First char of the title: { -> [.
Jan 20 2020
Ok, thank you for the review!
Added includes for vector, iota and shuffle.
Renamed writeUopsSnippetHtml() -> writeParallelSnippetHtml().
Jan 17 2020
Updated the comment.
Jan 16 2020
Thank you for the review.
@atanasyan Do you have any comment?
Jan 14 2020
Jan 13 2020
Removed leftover lines.
Dec 31 2019
Fixed typos.
Added a check of IssueCounters.
Dec 30 2019
Dec 27 2019
Dec 25 2019
Dec 19 2019
I have version 4.4.0+git47-g71166e2-1 so yes, I think this is the problem since the alias was added only after v4.6.0.
Dec 18 2019
Dec 17 2019
Dec 16 2019
Inlined Opcode.
Dec 13 2019
LGTM, thanks for the fix!
Dec 12 2019
@gchatelet @courbet How do you think the example I mentioned in the previous comment should be handeled on X86? This might inform us what (if anything) should be changed for MIPS.
Dec 10 2019
Dec 9 2019
Yes, other targets do have it but use it quite sparingly. X86 almost never uses it but there are some edge cases when parsing certain directives. For example, this line will trigger an assert fail because of an uninitialized TargetStreamer on X86:
echo ".cv_fpo_proc foo 4" | llvm-exegesis -mode latency -snippets-file=-
MIPS on the other hand uses TargetStreamer right at the start of the MipsAsmParser constructor and throughout the code used for parsing. The design of this MIPS code is quite different from other architectures (always relying on TargetStreamer or Assembler). I'm not sure if this was out of necessity or if it just evolved in to different path. Either way, the current code doesn't facilitate simple instruction extraction without all the necessary elements being in place.