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
No movement, so now? #10
Comments
Authors are academics and moved on to other projects I guess. I basically asked the same question in #6, got 19 likes but that does not help much... More than sad, it is scary that this was not merged in. Basically, it should be re-done from scratch with a current version of clang, too many changes since the author's version. And should be available in all compilers IMO. I did observe up to 20% performance drop in NFV scenarios using DPDK. Processing millions of packets per seconds, a sensible change in layout inside what is basically a small infinite loop processing packets can completely inverse a trend. But nobody cares enough. |
@tbarbette totally with you on that. Sadly I never worked with C/C++ or LLVM directly. Kind of new to rust but I'm totally into it. I don't have any experience in the field and getting started with the repository doesn't seem easy to me, but would love to help and if you have any entry points or tips for me I'm happy to have a go |
Hey @somehowchris -- are you still interested in porting the general idea of |
Would love to. My current struggles are:
(My laptop broke down and due to the chip shortage this might take a while) |
Hey @ccurtsinger,
Just listened to the presentation of Emery.
Now I would love to use it. Using it would make much more sence and reduce variance cause in many cases. (currently measuring tests with cargo bench, so not that great). Now yes, I read the readme, it says that the project isn't maintained. May I ask why?
Is there a plan/movement going for something new? did a miss an alternative? Would really love to see that thing fly and sure, if theres something to do or helpout I'm in.
Cheers 🍻
The text was updated successfully, but these errors were encountered: