fxysunshine opened a new pull request, #18015:
URL: https://github.com/apache/nuttx/pull/18015
## Summary
This pull request contains two compile warning in openlibm:
1. **Patch 5266499/2**: openlibm/src/k_rem_pio2.c:421:24: error: 'fq' may be
used uninitialized
* error: 'fq' may be used uninitialized [-Werror=maybe-uninitialized]
2. **Patch 5333599/1**: Building openlibm on x86_64 triggers two types of
compile warnings:
* attribute-alias: Incompatible type alias between `clog` and `clogl`
functions (s_clog.c:78:33)
* shadow: Declaration of `feclearexcept`/`fegetexceptflag` shadows built-in
functions (fenv_amd64.h:99:1, 117:1)
These patches have been validated internally and are ready for upstream
integration.
## Impact
- **Compatibility**: Maintains backward compatibility with existing code
- **Functionality**: No change to the behavior of math functions or FPU
exception handling; the warnings are false positives caused by openlibm's
compatibility layer.
- **Scope**: Only affects the compilation process of the openlibm library;
no runtime impact on library functionality or performance.
- **Compatibility**: No breaking changes to other modules or architectures;
the new flag is compatible with all supported toolchains (GCC/clang).
- **Toolchain**: Valid for GCC toolchains; no impact on clang builds (the
flags are ignored if not supported).
## Testing
✅ Build successful
✅ System boots correctly
✅ Core functionality verified
✅ No regressions detected
## Verification Checklist
- [x] Code compiles without warnings
- [x] No new issues introduced
- [x] x86_64 openlibm build completes without `attribute-alias` and `shadow`
warnings.
- [x] FPU exception handling functions (`feclearexcept`, `fegetexceptflag`)
work correctly.
- [x] Cross-architecture builds (ARM/RISC-V) are error-free.
- [x] No performance degradation in floating-point operations.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
