Page MenuHomeFreeBSD

RISC-V: fix some mismatched format specifiers
ClosedPublic

Authored by mhorne on Sep 4 2020, 12:24 AM.
Tags
None
Referenced Files
F151808959: D26319.id76764.diff
Fri, Apr 10, 7:57 PM
F151805083: D26319.diff
Fri, Apr 10, 7:20 PM
F151787804: D26319.id.diff
Fri, Apr 10, 4:32 PM
Unknown Object (File)
Thu, Apr 9, 11:45 PM
Unknown Object (File)
Thu, Apr 9, 9:35 PM
Unknown Object (File)
Tue, Apr 7, 3:18 PM
Unknown Object (File)
Tue, Apr 7, 8:46 AM
Unknown Object (File)
Tue, Apr 7, 8:43 AM
Subscribers

Details

Summary

RISC-V has been built with -Wno-format, which is how these went undetected.
Address them now before re-enabling those warnings.

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 33374
Build 30678: arc lint + arc unit

Event Timeline

mhorne created this revision.
arichardson added inline comments.
sys/riscv/riscv/db_disasm.c
419

Could also use %x since it's an int? How is this not triggering warnings with clang?

527

Same here?

sys/riscv/riscv/db_disasm.c
419

Yeah, that is better.

Looks like -Wno-format is passed when MK_FORMAT_EXTENSIONS == "no", so that would be why clang hasn't complained. I'm enabling it in D26320.

Address @arichardson's comment. Fix one additional instance in a riscv-specific driver.

This revision was not accepted when it landed; it landed in state Needs Review.Sep 8 2020, 1:21 PM
This revision was automatically updated to reflect the committed changes.