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

ulp_riscv_print: Add convenience function that supports different widths (IDFGH-12124) #13180

Closed
wants to merge 1 commit into from

Conversation

mickeyl
Copy link
Contributor

@mickeyl mickeyl commented Feb 14, 2024

ULP's print_hex is pretty handy, but hardcoded to uint32 with 8 digits. This patch adds a convenience function that supports different widths.

@CLAassistant
Copy link

CLAassistant commented Feb 14, 2024

CLA assistant check
All committers have signed the CLA.

Copy link

github-actions bot commented Feb 14, 2024

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello mickeyl, we appreciate your contribution to this project!


📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved, we synchronize it into our internal git repository.
4. In the internal git repository we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against 89413ea

@espressif-bot espressif-bot added the Status: Opened Issue is new label Feb 14, 2024
@github-actions github-actions bot changed the title ulp_riscv_print: Add convenience function that supports different widths ulp_riscv_print: Add convenience function that supports different widths (IDFGH-12124) Feb 14, 2024
@@ -37,6 +37,7 @@ void ulp_riscv_print_str(const char *str);
* @param Hex number to print
*/
void ulp_riscv_print_hex(int h);
void ulp_riscv_print_hex_with_number_of_digits(int h, int number_of_digits);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could you also add a function description to explain the purpose and the arguments?

@@ -49,3 +49,24 @@ void ulp_riscv_print_hex(int h)
h <<= 4; // move the 2nd leftmost byte to the left, to be extracted next
}
}

void ulp_riscv_print_hex_with_number_of_digits(int h, int number_of_digits)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Since the input here is int h, the maximum number of hex digits would be 8. In this case, I assume the purpose of this function would be to print < 8 bytes. Is the understanding correct?

{
int x;
int c;

Copy link
Collaborator

Choose a reason for hiding this comment

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

Would be good to add a sanity check for number_of_digits < 0 and number_of_digits >= 8. The first case should result in a error for the user and the second case should default the call to ulp_riscv_print_hex().

return;
}

// Does not print '0x', only the digits (8 digits to print)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
// Does not print '0x', only the digits (8 digits to print)
// Does not print '0x', only the digits specified by the number_of_digits argument

@sudeep-mohanty
Copy link
Collaborator

Thanks for the contribution @mickeyl! I've left some minor queries and comments. Once they are addressed, we should be good to merge. Thanks!

@mickeyl
Copy link
Contributor Author

mickeyl commented Mar 17, 2024

@sudeep-mohanty Thanks for your comments. I have rebuild the pull request putting them into account. Please have another look.

@sudeep-mohanty
Copy link
Collaborator

Hi @mickeyl, I do not see the updated changes. Maybe you missed committing them? 🤔

@mickeyl
Copy link
Contributor Author

mickeyl commented Mar 18, 2024

@sudeep-mohanty Indeed, my force-push didn't work for some reason. It should be visible now.

@sudeep-mohanty
Copy link
Collaborator

Thanks @mickeyl. Changes LGTM. I shall do some more tests and then merge it.

@sudeep-mohanty
Copy link
Collaborator

sha=89413eaab6501749f54072d80065c499b72c2c26

@sudeep-mohanty sudeep-mohanty added the PR-Sync-Merge Pull request sync as merge commit label Mar 18, 2024
@sudeep-mohanty sudeep-mohanty self-requested a review March 18, 2024 13:16
@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: NA Issue resolution is unavailable and removed Status: In Progress Work is in progress labels Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR-Sync-Merge Pull request sync as merge commit Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants