public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wdijkstr at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66946] Spurious uninitialized warning
Date: Tue, 21 Jul 2015 13:42:00 -0000 [thread overview]
Message-ID: <bug-66946-4-PMJIPBZhJX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66946-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946
--- Comment #4 from Wilco <wdijkstr at arm dot com> ---
(In reply to Andrew Pinski from comment #2)
> Comment on attachment 36021 [details]
> minimal example
>
> written == ((wchar_t) 0xfffd)
>
> Will ever be true or is there some sign extending going on which causes this
> to be false for the default case?
The issue seems related to signextension indeed. My GCC builds include this
patch: https://gcc.gnu.org/ml/gcc-patches/2015-05/msg00005.html
When I disable this new phase the warning disappears, so it might be due to a
transformation it makes. The generated code is virtually identical, just
different register allocation.
prev parent reply other threads:[~2015-07-21 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 16:25 [Bug tree-optimization/66946] New: " wdijkstr at arm dot com
2015-07-21 13:10 ` [Bug tree-optimization/66946] " wdijkstr at arm dot com
2015-07-21 13:28 ` pinskia at gcc dot gnu.org
2015-07-21 13:31 ` pinskia at gcc dot gnu.org
2015-07-21 13:42 ` wdijkstr at arm dot com [this message]
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=bug-66946-4-PMJIPBZhJX@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).