Skip to content
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

Replace insert/extract in scalar emulation with load/store #12

Open
edanor opened this issue Oct 21, 2015 · 0 comments
Open

Replace insert/extract in scalar emulation with load/store #12

edanor opened this issue Oct 21, 2015 · 0 comments

Comments

@edanor
Copy link
Owner

edanor commented Oct 21, 2015

Originally reported by: edanor (Bitbucket: edanor, GitHub: edanor)


Because we want to explicitly specialize only operations that can be expressed in specific instruction set, all unsupported operations should be left with resolution to scalar emulation.

Most of emulated functions are using insert/extract on a per-element basis. Performing insert/extract operations on vectors is slow for non-emulated vectors. Doing load/store on emulated data types shouldn't create any slow-downs due to compiler optimizations, and even if not, it will still reduce slow-down on target vector code.

This proposal is to re-write scalar emulation functions with LOAD/STORE instead of INSERT/EXTRACT.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant