Closed jerinphilip closed 2 years ago
@jerinphilip This is not a bug but the expected behavior. Because of the security reasons, currently the optimized gemm is only available to the privileged extensions and not to the normal web-pages (like the wasm test page).
Plus, you don't need to do anything to enable optimized gemm. It is on by default.
You can run the latest extension in the same nightly and can observe that optimized gemm is being used there 👍🏾
Closing this one as there is no need for any documentation. Optimized gemm is always on and it runs if it is available in the environment, otherwise fallback gemm runs. All of this is for privileged extensions in Firefox.
Closing this one as there is no need for any documentation. Optimized gemm is always on and it runs if it is available in the environment, otherwise fallback gemm runs. All of this is for privileged extensions in Firefox.
@abhi-agg Perhaps you don't realize this, right now I'm tracking Bugzilla and GitHub issues for what should ideally be documentation. There is only @kpu who knows the complexities of GEMM Mozilla connects, I know partially because of undertaking MozIntGemm (ARM). I'm fairly certain others (at least at Edinburgh) have very little clue on what exactly is going on at this stage. It is expected that you check-in documentation for future users of the optimized gemm, and what the future of features like WORMHOLE, native intrinsic based gemm etc. are.
I'm working with 9eb2437. I am using Firefox Nightly (2022-02-19; 99.0a1) on Windows 11.
Using the build-wasm.sh script, which appears to be reporting success patching the "import-intgemm" module thing:
Now I navigate according to instructions to use the built artefacts:
See screenshot:
Checked
about:config
forgemm
and found the following:Perhaps this is a nightly bug, in any case filing this here as documentation is missing and to be forwarded to the correct place.
cc: @abhi-agg