This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch soft-fp]: Possibly use of uninitialized variables
- From: Kai Tietz <Kai dot Tietz at onevision dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Kai Tietz <ktietz70 at googlemail dot com>
- Date: Mon, 18 Oct 2010 14:46:49 +0200
- Subject: Re: [patch soft-fp]: Possibly use of uninitialized variables
gcc-patches-owner@gcc.gnu.org wrote on 18.10.2010 13:50:43:
> On Mon, 18 Oct 2010, Kai Tietz wrote:
>
> > Hello,
> >
> > This fixes some potential uses of unitialized variables, which I got
> > reported by gcc 3.4.4 while bootstrap and it seems right by its
> > detection.
>
> Please see codingconventions.html. soft-fp patches must always go in
> glibc first with unmodified glibc code then being imported into GCC.
>
> In this case, see <http://sourceware.org/bugzilla/show_bug.cgi?id=10114>
-
> you'll need to work out a fix on the lines of what the last comment
> indicates.
Well, I see that this problem is already addressed for a year. I have to
admit that soft-fp build for targets, which aren't based on glibc, is a
bit loud due unprototyped functions and some potential uninitialized
variables, but all in all nothing serious. So I am patient that this
latent issues get fixed on glibc.
> This code should never be built with 3.4.4 anyway; it's target code that
> should only be built by the newly built compiler.
Yes, sorry for being unclear here. Of course warning is shown by produced
4.6 based compiler.
> --
> Joseph S. Myers
> joseph@codesourcery.com
>
Regards,
Kai