On 7/31/23 08:52, Kito Cheng via Gcc-patches wrote:
On Mon, Jul 31, 2023 at 10:03 PM Maciej W. Rozycki <ma...@embecosm.com> wrote:
On Mon, 31 Jul 2023, Kito Cheng wrote:
Sorry for disturbing, pushed a fix for that, and...added
-Werror=unused-variable to my build script to prevent that happen
again :(
I just configure with `--enable-werror-always', which we want to keep
our standards up to anyway,
I rely on the host GCC which is 11 relatively old compared to the
trunk, so --enable-werror-always will get many -Wformat* warning :(
but if you find this infeasible for some
reason with your workflow, then there's always an option to grep for
warnings in the build log and diff that against the previous iteration.
That's a good suggestion! Thanks, let me try to apply myself workflow :)
I'm thinking that as part of the CI POC being done by RISE that the base
AMI image ought to be gcc-13 based and that we should configure the
toolchains we build with -enable-werror-always.
While we can't necessarily get every developer to embrace this workflow,
we ought to be catching it quicker than we currently are.
jeff
