-
Notifications
You must be signed in to change notification settings - Fork 7.7k
fix(ltoa): Use proper labs
for long values and fix affected sketches detection
#11814
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
Conversation
labs
for long values
👋 Hello lucasssvaz, 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 ...
Review and merge process you can expect ...
|
Test Results 76 files 76 suites 13m 11s ⏱️ Results for commit cddf76f. ♻️ This comment has been updated with latest results. |
labs
for long valueslabs
for long values and fix affected sketches detection
Memory usage test (comparing PR against master branch)The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.
Click to expand the detailed deltas report [usage change in BYTES]
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a type mismatch bug in the ltoa
function and improves function signature normalization in the affected sketches detection script. The changes ensure proper handling of long values and more robust matching of function declarations regardless of parameter naming differences.
- Changed
abs()
tolabs()
inltoa
function to correctly handle long integer absolute values - Added comprehensive function signature normalization to handle parameter name differences
- Updated qualified name building to use normalized signatures for better function matching
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
cores/esp32/stdlib_noniso.c | Fixed type mismatch by using labs() instead of abs() for long values |
.github/scripts/get_affected.py | Added signature normalization function and integrated it into qualified name building |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
1766b62
to
cddf76f
Compare
Description of Change
This pull request introduces improvements to function signature normalization in the
.github/scripts/get_affected.py
script and fixes a minor bug in theltoa
implementation for the ESP32 core. The main focus is on ensuring that function signatures are compared based on their types rather than parameter names, which helps in matching function declarations and implementations even if parameter names differ.Signature normalization improvements
normalize_function_signature
to.github/scripts/get_affected.py
that strips parameter names from function signatures, retaining only the types. This helps in matching functions regardless of parameter name differences and handles cases like default parameters and const qualifiers.build_qname_from_tag
in.github/scripts/get_affected.py
to use the new signature normalization function, ensuring that qualified names are constructed with normalized signatures.Bug fix in ESP32 core
abs(value)
tolabs(value)
incores/esp32/stdlib_noniso.c
to correctly compute the absolute value of along
type, fixing a type mismatch bug.Test Scenarios
Tested locally