- User Since
- Sep 9 2019, 7:00 PM (12 w, 2 d)
Sun, Dec 1
Adding testcase for scalar_math_patterns and AVX512_scalar_math_fp_patterns.
Moving setOperationAction(ISD::STRICT_FADD/STRICT_FSUB/STRICT_FDIV/STRICT_FMUL, MVT::v2f64, Legal) into SSE2 judgment statement.
Tue, Nov 26
Add option to the tests.
Mon, Nov 25
Pengfei has helped me commit the test cases.
I rebase and add the option "-disable-strictnode-mutation" to the test case.
STRICT_FP_ROUND has been set as custom so I remove setting it as legal. When entering the custom processing function, if the operand type is legal,the function behaves the same as setOperationAction(ISD:STRICT_FP_ROUND, TYPE, legal)
Modify the test case. Since we do not disable sse, we can pass float-pointer value by register instead of passing by pointer.
Thu, Nov 21
Thanks for all of your help.
Wed, Nov 20
@uweigand Thank you, now I get clear of the logic there. I add some of your comment to the original comments in the code, I think it may helps us understand this code better. Or we still keep the previous comments?
update comments and fix a bug
update the comments
Tue, Nov 19
@uweigand Thanks for your help.
Mon, Nov 18
Fix format problem.
Update as comments.
I'm not sure if there's a possibility: some normal float operations of a backend is not Expand,
but they may think expanding strict-float operation can meet their requirements.
Although I haven't found a case yet.
Binding the value of DisableStrictNodeMutation to flag IsStrictFPEnabled, updating as comments.
Sun, Nov 17
Fri, Nov 15
@uweigand Thanks for your review. I have added information to see if the target supports strict float, so systemZ can disable strictnode mutation as default.
This patch add an variable EnableStrictNode to the TargetLoweringBase to determine whether the target already supports the strict float operation.
Modify the patch @uweigand's suggestion.
Thu, Nov 14
Wed, Nov 13
I am working on STRICT_FP_TO_SINT/UINT, too. For now, Pengfei and I thought we can set promotion as custom so we can promote the type in x86 without affecting other backend. What do you think?
Tue, Nov 12
OK, I 'll make a try.
Modify the name of tests
Modify the name of tests and delete some RUN line in fp80-strict-scalar.ll.
Mon, Nov 11
Rebase and change the name of tests in fp-strict-scalar.ll . Add a test file which only process 80-bit long double type, because tests for 80-bit FP is complex to put into fp-strict-scalar.ll without changing the '–check-prefix'.
Nov 3 2019
Oct 31 2019
This patch fix the broken test: CodeGen/ms-inline-asm.c.
Oct 29 2019
I am sorry I updated two wrong versions. The Diff 226862 is right version.
The Diff 226855 has some problems. This one adds testcase to verify if x87 instructions use/def fpcw and fpcw registers.
Add testcase to verify if x87 instructions use/def fpcw and fpcw registers.