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

Move Common.py to module #1607

Merged
merged 48 commits into from
Feb 13, 2025
Merged

Move Common.py to module #1607

merged 48 commits into from
Feb 13, 2025

Conversation

bstefanuk
Copy link
Contributor

Moves Common.py into a module, breaking up various elements into self-contained files.

@bstefanuk bstefanuk self-assigned this Jan 31, 2025
ellosel
ellosel previously approved these changes Feb 9, 2025
@KKyang
Copy link
Contributor

KKyang commented Feb 10, 2025

There are a lot of unrelated files in the PR. Can we remove them?

* fix: purge library-print-debug
* feat: make build paths static
* feat: remove 'SortProblems' global param
* feat: remove 'ExpandRanges' global param
* feat: remove 'WavefrontWidth' global param
* feat: remove 'ValidateLibrary' global param
* feat: remove 'EnableHalf' and 'ClientArgs' global params
* feat: prefer profile decorator over 'Profiler' global param
* chore: remove 'LibraryPrintDebug' from build_client.yaml
* feat: remove 'MaxFileName' from global params
@bstefanuk
Copy link
Contributor Author

bstefanuk commented Feb 11, 2025

@KKyang You bet, I'll remove the files from the clients/ and library/ directories. These are here because I'm running the pre-commit hook in .githooks/ and they're automatically indexed when I fix merge conflicts. Could I request that those on your team consider using the pre-commit so that this side-effect can be avoided.

jichangjichang
jichangjichang previously approved these changes Feb 11, 2025
Copy link
Collaborator

@jichangjichang jichangjichang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please get CI passed before merging.

@KKyang
Copy link
Contributor

KKyang commented Feb 11, 2025

@KKyang You bet, I'll remove the files from the clients/ and library/ directories. These are here because I'm running the pre-commit hook in .githooks/ and they're automatically indexed when I fix merge conflicts. Could I request that those on your team consider using the pre-commit so that this side-effect can be avoided.

Files not modified should not have any changes. If you trigger the hook using git commit, it won't affect unmodified files.

@bstefanuk
Copy link
Contributor Author

bstefanuk commented Feb 11, 2025

This isn't true, because the files are touched when resolving a merge conflict, they're still updated by the precommit.

ellosel
ellosel previously approved these changes Feb 11, 2025
@bstefanuk bstefanuk dismissed stale reviews from ellosel and jichangjichang via e4939f7 February 12, 2025 17:57
@KKyang KKyang merged commit f45e5b9 into ROCm:develop Feb 13, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants