public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55035] reload1.c:3766:41: error: ‘orig_dup[0]’ may be used uninitialized in this function (for fr30, microblaze, moxie, rl78)
Date: Sun, 27 Jul 2014 22:29:00 -0000 [thread overview]
Message-ID: <bug-55035-4-u0WXgkXUXo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55035-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55035
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed|2013-02-27 00:00:00 |2014-07-27
Ever confirmed|0 |1
Known to fail| |4.8.0, 4.9.1
--- Comment #1 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Also seen for gcc-4.9.1 ppc64-linux host (gcc110) same targets this far
(considering the PR author probably same script, config-list.mk; except with
ada removed).
next prev parent reply other threads:[~2014-07-27 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 14:23 [Bug middle-end/55035] New: reload1.c:3766:41: error: ‘orig_dup[0]’ may be used uninitialized in this function (for fr30, microblaze) amylaar at gcc dot gnu.org
2014-07-27 22:29 ` hp at gcc dot gnu.org [this message]
2014-07-27 22:31 ` [Bug middle-end/55035] reload1.c:3766:41: error: ‘orig_dup[0]’ may be used uninitialized in this function (for fr30, microblaze, moxie, rl78) hp at gcc dot gnu.org
2014-07-29 11:05 ` hp at gcc dot gnu.org
2015-04-09 19:16 ` aldot at gcc dot gnu.org
2015-05-20 1:06 ` miyuki at gcc dot gnu.org
2015-07-26 8:57 ` miyuki at gcc dot gnu.org
2015-07-27 15:43 ` law at redhat dot com
2015-08-13 20:23 ` rsandifo at gcc dot gnu.org
2015-08-26 7:28 ` ro at gcc dot gnu.org
2015-09-09 0:36 ` hp 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-55035-4-u0WXgkXUXo@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).