[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available

2019-03-27 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=405430 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available

2019-03-25 Thread Petar Jovanovic
https://bugs.kde.org/show_bug.cgi?id=405430 --- Comment #3 from Petar Jovanovic --- (In reply to Mark Wielaard from comment #0) > I would like to enable -Wimplicit-fallthrough=2 by default when available. > It was introduced in GCC7. It caught a couple of bugs, but it does need a > bit of extra

[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available

2019-03-13 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=405430 Mark Wielaard changed: What|Removed |Added CC||c...@us.ibm.com -- You are receiving this

[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available

2019-03-13 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=405430 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available

2019-03-13 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=405430 --- Comment #1 from Julian Seward --- +1 for this; I am all in favour of more compile-time analysis. As far as the guest_mips_toIR.c fallthrough goes, I'd guess it is intended. I say this because it looks as if all 3 of case 0xA: /* LX */