From: Bernd Schmidt <bernds@codesourcery.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Initialize previous in read_state_param_structs
Date: Mon, 30 May 2011 11:50:00 -0000 [thread overview]
Message-ID: <4DE370EA.1000501@codesourcery.com> (raw)
In-Reply-To: <ork4d8348z.fsf@livre.localdomain>
On 05/30/2011 11:51 AM, Alexandre Oliva wrote:
> Bootstrap-O3 complains about uninitialized uses of this variable in
> gengtype-state.c. The variable can never actually be used before
> initialization, but GCC is not smart enough to realize that.
> read_state_structures, just before the function at hand, has a similar
> loop and it zero-initializes both head and previous, so I adjusted the
> affected function to follow the same pattern and avoid the bogus
> warning. Regstrapped on x86_64-linux-gnu and i686-pc-linux-gnu. Ok to
> install?
Ok. Alternatively you could fix the warning and shorten the code using
the pprev trick.
Bernd
next prev parent reply other threads:[~2011-05-30 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 10:56 Alexandre Oliva
2011-05-30 11:50 ` Bernd Schmidt [this message]
2011-06-04 3:16 ` Jack Howarth
2011-06-04 10:21 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE370EA.1000501@codesourcery.com \
--to=bernds@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).