Disable warnings as errors until we move to GCC 13

[ktf]

Disable warnings as errors until we move to GCC 13

-Wno-error=dangling-reference is available only there.

[ktf]

As expected, enabling the warnings as errors breaks as soon as we move to a new compiler. Disabling for now until we merged GCC 13.

[davidrohr]

I don't fully understand why youbwrite until we merge gcc 13. Won't we still have the wrong warning with gcc 13? Btw, instead of fully disabling all warnings you can use gcc's #pragme diagnostic to disable selected warnings in single files for some lines.

[ktf]

The issue is that the warning is new, so passing -Wno-error=dangling-reference only works if we are at GCC 13. I prefer not to pollute code in with pragma diagnostic, if a temporary solution in alidist brings us where we want.

[vkucera]

@ktf @ddobrigk

• Was this communicated to the community (WP14+WP4 meeting, email, Mattermost)? I don't see any announcement about this.
• Why was it not reverted immediately after merging Migrate to GCC 13 #5541 ?
• Why has it not been reverted yet? (more than a month after fixing the reason for merging it!)
• After enabling the warnings as errors now, many PRs in O2Physics will fail because of unrelated warnings accumulated over the last month and people will have to fix them even though they didn't introduce them. How can we avoid this in the future?