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

cpu: x64: brgemm: use range-based loop for jit_brgemm_amx_uker.cpp #2091

Merged

Conversation

Permanence-AI-Coder
Copy link
Contributor

Description

The code changes in this PR were generated automatically by the Permanence AI Coder and reviewed by @eelenberg and @jweese. This PR replaces iteration-based for loops over members of tloop with range-based for loops, which removes unnecessary indexing variables, improves readability, and reduces potential off-by-one errors. This PR is effectively applying the update from #2086 to an additional file.

on-behalf-of: @permanence-ai [email protected]

Checklist

General

  • Do all unit and benchdnn tests (make test and make test_benchdnn_*) pass locally for each commit?
  • Have you formatted the code using clang-format?

@Permanence-AI-Coder Permanence-AI-Coder requested a review from a team as a code owner September 11, 2024 19:51
@github-actions github-actions bot added the platform:cpu-x64 Intel64/AMD64 processors. Codeowner: @oneapi-src/onednn-cpu-x64 label Sep 12, 2024
@vpirogov vpirogov added this to the v3.7 milestone Sep 12, 2024
@mgouicem
Copy link
Contributor

It seems to be a purely stylistic change. Given that PR review and merging is a rather manual work, we would be grateful if you could focus on more impactful changes (e.g. improving safety of the library, or fixing actual issues).
Thanks.

@spalicki spalicki merged commit 7f5e066 into oneapi-src:main Oct 3, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform:cpu-x64 Intel64/AMD64 processors. Codeowner: @oneapi-src/onednn-cpu-x64
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants