This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Fix PR39799: missing uninitialized vars warning
- From: Manuel López-Ibáñez <lopezibanez at gmail dot com>
- To: Bernd Schmidt <bernds at codesourcery dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 30 Jun 2010 11:26:33 +0200
- Subject: Re: Fix PR39799: missing uninitialized vars warning
- References: <4C2B0B37.70209@codesourcery.com>
On 30 June 2010 11:15, Bernd Schmidt <bernds@codesourcery.com> wrote:
> This is a problem that was introduced with the fix for PR31081. ?Looking
> at that PR's history, it seems the inliner has problems with overlapping
> lifetimes for things where SSA_NAME_OCCURS_IN_ABNORMAL_PHI.
>
> The solution was to zero-initialize all uninitialized variables when
> inlining. ?This disables warnings for them, which is the regression in
> PR39799.
>
> I've bootstrapped and regression tested the patch below on i686-linux.
> This limits the zero-initialization to variables with
> SSA_NAME_OCCURS_IN_ABNORMAL_PHI. ?I doubt register pressure is an issue
> since we have another rtl-based init-regs pass. ?Ok?
+/* { dg-message "note: '\[^\n'\]*' was declared here" "note:
expected" { target *-*-* } 0 } */
Why not put this in the proper line?
Does this work at -O{0,1,3,fast,s}? If so, why not put it in torture
tests? Otherwise, I would still suggest to put it in c-c++-common.
Manuel.