-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[DAG] TargetLowering::expandABD - investigate alternative expansions #84639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:
If you have any further questions about this issue, don't hesitate to ask via a comment in the thread below. |
@llvm/issue-subscribers-good-first-issue Author: Simon Pilgrim (RKSimon)
As mentioned here by @jayfoad https://github.com//pull/84431#issuecomment-1986043833
> Incidentally Hacker's Delight has a section "Average of Two Integers" which has some neat tricks for implementing these operations without extending to N+1-bit integers. These include alternative code for targets with poor MIN/MAX/SAT/CMPSEL instructions as well as simpler expansions depending upon the knownbits/numsignbits of the operands. |
Hey @RKSimon, I would like to work on this. |
Hi I would like to work on this if this is available |
@changkhothuychung: Just create pull request and mention it on this page. |
Does this issue aim to look at both the optimization of "Average of two integers" or only alternative code targets for absolute difference in the TargetLowering.cpp file? The description of the issue also seems a little open to me. Can you please refine it with fine-grained tasks? In the original thread, a dev mentioned this :
I don't see why we would want to implement AvgFloor in TargetLowering::expandABD. If I am not wrong, the optimizations that were introduced in |
Closing this as it references the wrong lowering code, is too broad and rather confusing - I'll create more useful smaller issues. |
Right, that's what I thought, was scratching my head all morning :) Nevertheless, found some interesting resources on compiler optimization. |
As mentioned here by @jayfoad #84431 (comment)
These include alternative code for targets with poor MIN/MAX/SAT/CMPSEL instructions as well as simpler expansions depending upon the knownbits/numsignbits of the operands.
The text was updated successfully, but these errors were encountered: