User Details
- User Since
- Sep 28 2015, 3:57 AM (390 w, 6 d)
Oct 26 2018
Oct 9 2018
kind ping?
Oct 8 2018
Sep 3 2018
Aug 31 2018
Aug 30 2018
Aug 21 2018
Hi Chandler, are you still planning to work on that?
Aug 17 2018
Thanks for the fix. LGTM
Aug 2 2018
Aug 1 2018
Hi Roman, I would prefer to do it as separate patches: the first one for Value splitting routine and the second for one splitToValueTypes
Thanks for your comments. Indeed the struct handling is not very well covered with tests in x86. I added the tests for cases, which are supported now
Jul 31 2018
Jul 27 2018
Thanks, I submitted this idea for a review here: https://reviews.llvm.org/D49913
Jul 26 2018
In a lot of cases, we would like to treat MoveReg-type instructions and generic COPY instruction in the same way.
E.g. in this code:
Jul 25 2018
Jul 23 2018
Jul 11 2018
the fix is committed as rL336703. Sorry about the duplication
added context
Jul 10 2018
Jun 5 2018
Jun 4 2018
Jun 1 2018
May 29 2018
May 21 2018
added context
May 18 2018
May 8 2018
Apr 24 2018
Apr 19 2018
glad to help :)
Apr 16 2018
Mar 14 2018
Mar 13 2018
Added context
added context
Right, sorry about that. One sec
Fix for a typo:
Mar 12 2018
Mar 5 2018
Feb 28 2018
Feb 27 2018
addressed comments. Added legalizer and general tests
Feb 22 2018
added legalizer tests
Added tests for legalizer
Feb 15 2018
Right, sorry about that. So the fix is committed as rL325135
Feb 14 2018
Provided context
That makes sense, thanks for the comments. In the new version there is a change in compress_expand.ll, which in my view is ok
The problem originated from a miscompare in a benchmark. That appeared to be a machine-scheduler that moved writes after reads of a pointer. It turned out that the scheduler was within its rights to do so, as it checked the offset of the following pointer:
Feb 13 2018
Feb 8 2018
X86 part is submitted. All ready to go :)