[PING] [PATCH] S/390: Do not turn maybe-uninitialized warnings into errors

[Jeff Law]

On 10/28/20 3:38 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
> On Mon, Oct 05, 2020 at 02:02:57PM +0200, Stefan Schulze Frielinghaus via Gcc-patches wrote:
>> On Tue, Sep 22, 2020 at 02:59:30PM +0200, Andreas Krebbel wrote:
>>> On 15.09.20 17:02, Stefan Schulze Frielinghaus wrote:
>>>> Over the last couple of months quite a few warnings about uninitialized
>>>> variables were raised while building GCC.  A reason why these warnings
>>>> show up on S/390 only is due to the aggressive inlining settings here.
>>>> Some of these warnings (2c832ffedf0, b776bdca932, 2786c0221b6,
>>>> 1657178f59b) could be fixed or in case of a false positive silenced by
>>>> initializing the corresponding variable.  Since the latter reoccurs and
>>>> while bootstrapping such warnings are turned into errors bootstrapping
>>>> fails on S/390 consistently.  Therefore, for the moment do not turn
>>>> those warnings into errors.
>>>>
>>>> config/ChangeLog:
>>>>
>>>> 	* warnings.m4: Do not turn maybe-uninitialized warnings into errors
>>>> 	on S/390.
>>>>
>>>> fixincludes/ChangeLog:
>>>>
>>>> 	* configure: Regenerate.
>>>>
>>>> gcc/ChangeLog:
>>>>
>>>> 	* configure: Regenerate.
>>>>
>>>> libcc1/ChangeLog:
>>>>
>>>> 	* configure: Regenerate.
>>>>
>>>> libcpp/ChangeLog:
>>>>
>>>> 	* configure: Regenerate.
>>>>
>>>> libdecnumber/ChangeLog:
>>>>
>>>> 	* configure: Regenerate.
>>> That change looks good to me. Could a global reviewer please comment!
>> Ping
> Ping

I think this would be a huge mistake to install.


Jeff