User Details
- User Since
- Mar 24 2016, 3:59 AM (375 w, 2 d)
Wed, May 31
Tue, May 30
Wed, May 24
Mon, May 22
address review comments
fix release note placemenfix release note placement
Tue, May 16
Sun, May 14
Wed, May 10
Apr 21 2023
Let's submit this quick fix first and we can re-enable it after your other patch.
I wanted gchatelet@ to have a look at this, because he wrote the Instruction/Operand code. In particular, I'm wondering why we're not using the info on the actual Operand value rather than relying on the MCOperandInfo for the operand. Specifically, we do know that this is a register since we return true for isReg, so we could just bake this knowledge into getExplicitOperandInfo in a target-independant way.
Apr 18 2023
Apr 13 2023
Apr 7 2023
Thanks for the review.
Thanks for the data. Can you get someone to approve that the size change is OK ? Otherwise LGTM for the exegesis part.
Fix release note placement and phrase it more consistenly with other notes in that section.
Apr 6 2023
- Address review comments
- Add release notes.
ping
Apr 2 2023
No strong opinion on this, if you feel that's better that's fine with me.
Thanks for the patch.
Mar 27 2023
In principle I like that, however this has implications on the size of the various llvm binaries. Can you please measure the increase in binary size for e.g. clang ?
This is great, thanks for the patch.
Mar 20 2023
Mar 19 2023
Thanks. In principle that sounds goods, my only real remark is about what flags we use to communicate that intent to the tool.
Mar 10 2023
I don't think JIT'ing X86 modules on SystemZ is supported.
Mar 2 2023
Feb 3 2023
Jan 27 2023
This one is NFC, tag it as such ?
Jan 24 2023
Jan 23 2023
add matcher to registry and add release note
ping
Jan 17 2023
Regenerate doc
fix doc
fix ddoc
Jan 16 2023
Are you seriously saying that 10x wallclock improvement is negligible?
Jan 13 2023
Jan 11 2023
Do we really need the speed boost ? My worry is that we are making the code more complex for a negligible advantage. I personally have never felt that waiting for a couple of minutes was really an issue, but you might have other use cases in mind ?
Jan 9 2023
Jan 6 2023
I think we should keep a single one, but just to bikeshed, a TypeSize has a Value, not a Size, so I would keep getFixedValue.
Jan 4 2023
Nice, thanks.
Jan 3 2023
The code in this patch looks good to me, and I think it turned easier to read than the LinearPoly* abstractions. So unless there is a good reason to keep them, LGTM.