-
Notifications
You must be signed in to change notification settings - Fork 0
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
oneDNN enablement and 8 bit GEMM support for s390x #1
Comments
Hi, could you elaborate further about the requirements for this feature? |
Resolved with pull request oneapi-src#1551 . |
@edelsohn , please note that bountysource did not cashout this (and other) bounties. |
@abebeos Other bounty hunters have alerted me to the problem and I have been discussing the issue with Bountysource, The Blockchain Group (the current owner of Bountysource, a French company publicly traded on the EuroNext exchange), and the VC investors in The Blockchain Group for the past few months. The Blockchain Group repeatedly promises me that they will pay the bounties, but nothing happens. The Blockchain Group commented that they have a concern about the accounts, but refuse to provide details or cooperate with me to investigate and resolve the concern. I have confirmed to them that the bounty hunters and bounty values are correct. The bounty funds have been correctly credited to the bounty hunters within the Bountysource system and IBM had paid the invoices to fund the bounties, so I and IBM have limited recourse. It it curious why The Blockchain Group has not been able to fulfill these financial obligations of the bounty cashouts. |
@edelsohn, as things stand, I believe one can safely assume that bountysource/Blockchain Group embezzles the escrowed bounty funds (e.g. using the money somewhere else, like investing/loosing-it in crypto etc.). |
Enable oneDNN for s390x and add 8 bit GEMM support optimized for s390x.
The text was updated successfully, but these errors were encountered: