Closed michaelweiser closed 4 years ago
gcc again... Thanks for reporting this. I'll have a look at it.
Do you happen to know whether this also occurs with the stable-0.6.0 and stable-0.7.0 branches?
Yes, it does (I needed to cherry-pick 0d22a7aea2eb0851d406eaf0c4d6a7a18c033bcc and 49f3b55de9c7fdfec8cdae49976ce61978890f17 to fix the other compiler errors under gcc-10 for the stable-0.6.0 branch)
@salahcoronya Thanks. Backporting those patches to stable-0.6.0: https://github.com/stefanberger/libtpms/pull/134
@michaelweiser Merged the fix.
Works a treat. Thank you!
With gcc 10.1.0 I get with current master:
The following change silences the warning but I'm unsure if it's semantically correct: