On Fri, Aug 02, 2024 at 11:41:05AM -0500, Dan Carpenter wrote: > 2) I get some weird precedence issues where Smatch is taking code like: > "(a == b) == (c == d)" and changing it to "*a == b == *c == d". > I don't even know how that's happening and how does Smatch think > we're dereferencing integers? I'm still working on this. These bugs have also disappeared. So so strange. There is definitely a bug in Smatch, but I guess the min/max changes no longer trigger it. (min/max was being tweaked and updated every day.) I feel like I have seen this bug occasionally before. I'll look into it next week. regards, dan carpenter
