public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61869] Spurious uninitialized warning
Date: Mon, 21 Jul 2014 19:16:00 -0000 [thread overview]
Message-ID: <bug-61869-4-ilG19nvZtu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61869-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61869
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-07-21
CC| |manu at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Yury Gribov from comment #0)
> Created attachment 33167 [details]
> /home/ygribov/repro.i:30:12: warning: ‘*((void*)& i +8)’ may be used
> uninitialized in this function [-Wmaybe-uninitialized]
Sad we are still printing this **** to the user (even if the warning were
valid)
>From gcc-bugs-return-456882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 21 19:22:50 2014
Return-Path: <gcc-bugs-return-456882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14778 invoked by alias); 21 Jul 2014 19:22:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14712 invoked by uid 48); 21 Jul 2014 19:22:45 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61396] [4.10 regression] ICE in simplify_immed_subreg
Date: Mon, 21 Jul 2014 19:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61396-4-FATCYM3kDE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61396-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61396-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-07/txt/msg01473.txt.bz2
Content-length: 285
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida396
--- Comment #4 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #3)
> Revision r209530 is OK, r210534 is not, likely a wide-int fallout.
>
The problem first appeared in trunk revision 210113.
next prev parent reply other threads:[~2014-07-21 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 14:05 [Bug tree-optimization/61869] New: " y.gribov at samsung dot com
2014-07-21 19:16 ` manu at gcc dot gnu.org [this message]
2021-03-29 22:00 ` [Bug tree-optimization/61869] Spurious uninitialized warning (lim1 pass, pretty-printed internal var) msebor at gcc dot gnu.org
2021-03-29 22:01 ` cvs-commit at gcc dot gnu.org
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-61869-4-ilG19nvZtu@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).