From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27773 invoked by alias); 20 Jun 2007 16:25:39 -0000 Received: (qmail 27476 invoked by uid 48); 20 Jun 2007 16:25:25 -0000 Date: Wed, 20 Jun 2007 16:25:00 -0000 Message-ID: <20070620162525.27475.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/31688] Bogus "may be used uninitialized" warning In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "burnus at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-06/txt/msg01727.txt.bz2 ------- Comment #4 from burnus at gcc dot gnu dot org 2007-06-20 16:25 ------- > Tobias, could you reopen this bug (I can't). This is different from PR 5035. > Whereas PR 5035 warns about variables present in the users code, these warnings > come from frontend generated variables Well, for the middle end it is all the same. > These warnings are thus needlessly confusing and supposedly can be > easily supressed by giving them proper attributes in the fronted. I don't know how one should properly handle these in the front end (without unneeded initialization of variables), but I reopened the bug and moved it to the Fortran front end. -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Component|middle-end |fortran Resolution|DUPLICATE | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31688