- User Since
- Oct 19 2012, 12:57 AM (343 w, 4 d)
Can expectedCost ever return zero?
Wed, May 8
looks obviously good to me. thanks!
Tue, Apr 30
Wed, Apr 24
Apr 15 2019
Apr 13 2019
Apr 6 2019
Apr 5 2019
Mar 20 2019
Mar 19 2019
Mar 16 2019
I'm curious as to how will we generate these flags.
Mar 13 2019
The concept of "hacked" is lost when you move up to TTI. I'd change the logic to reflect that this is making it "prohibitively expensive" instead of "hacked value".
Mar 7 2019
I'm not against moving docs there but I think there should be a conversation about the broader subject of docs, github, wiki, etc.
Feb 27 2019
Hi @steleman, that wasn't a "loaded question", it was an honest one. Let me try to clarify what that means for all parties.
Feb 19 2019
Feb 18 2019
@t.p.northover Is this the correct behaviour for Apple's syntax?
Sorry for the delay, this fell out of my radar and just saw the ping now.
Feb 16 2019
Feb 15 2019
Thanks Stephan, now looks good.
Thanks for your answers, they make sense. Other than the mistake I made on disabling exp calls (you were right), looks fine.
Feb 14 2019
Feb 13 2019
Funny thing is, SVML is also only supported, AFAIK, for Intel. I agree that we should emit errors, but we should also emit a similar error on SVML.
I have a few comments inline, mostly harmless, as the change is almost entirely mechanical and makes sense.
Feb 9 2019
Right, this is a completely different patch and it seems that the original proposal hadn't been tested thoroughly.
Since the previous version was approved already, I'm "requesting changes" so that we can look at it again, together with D53927 to make sure it's still the right way to go.
Feb 8 2019
Adding llvm-commits for wider audience
Feb 6 2019
Jan 31 2019
dword is indeed widely used. I'm surprised we didn't support that yet. Apparently, neither does Arm, only X86, Mips and RiscV.
Jan 30 2019
Jan 29 2019
Jan 23 2019
Jan 22 2019
Sounds good. Please add simple tests for +inf and -inf on both double and float. Perhaps also float to double and vice versa from the IR constant (like the changed test shows), too. Thanks!
Jan 20 2019
Hal approved the Clang side, so this one looks good, too.
Jan 10 2019
Perhaps best to ping Clang's commit, as that's the review that is blocking this one.
Dec 19 2018
Thanks! I've updated the reviewers on the Clang review (D53928).
Adding clang/omp developers for proper review. Please feel free to add more.
Dec 17 2018
If you git log cmake/config.guess you'll see that all the past changes either remove functionality or add obvious parts that shouldn't inflict on copyright.
Dec 14 2018
Right, that's all very hypothetical, but the change is harmless otherwise and generally an improvement of the code. I can't see any impact this would have in code generation or compilation time, so LGTM.
Getting a bit late in this discussion, as we had an internal one just recently.
Dec 13 2018
Right, I'm happy with the patch and will let @fhahn do the final review and approval. Thanks!
Dec 12 2018
As a starting point, this sure looks good to me. Thanks!
Dec 11 2018
Overall, this change looks ok to me. The tests look good, too.
Dec 7 2018
Adding more folks due to the license issue.
Dec 5 2018
Dec 3 2018
Right, that one is a hairy test, and I can see how this would break that test if not right. :)
Dec 1 2018
That's very useful, thanks! LGTM.
Nice clean solution, thanks!
Nov 30 2018
Accepting as this seems to fix the fast-math issue that was the reason why we reverted. Let me know if this still breaks things.
Nov 25 2018
This makes sense to me, but I'm not well versed in LLDB testing. Adding Pavel and Omair to approve it.
Nov 23 2018
LGTM, do we have any tests for llvm-mc output?
Nov 21 2018
I'm not sure what's the supposed behaviour on Apple syntax, but the tests show both apple and eabi syntax changing to the recommended encoding, so this LGTM.
Nov 14 2018
@Carrot, can you check if this fixes the fast math issues on your side, please?
Nov 13 2018
Perfect, LGTM. Thanks!
So, IIUC, the way you only get the interleave info on instructions and map to VPlan is because we don't yet have scalar evolution in VPlan, so we need to do that in Instruction and then map to VPInstruction.
Nov 12 2018
Just had a look again and it's looking great, thanks Florian!