public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55035] New: reload1.c:3766:41: error: ‘orig_dup[0]’ may be used uninitialized in this function (for fr30, microblaze)
Date: Tue, 23 Oct 2012 14:23:00 -0000	[thread overview]
Message-ID: <bug-55035-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55035

             Bug #: 55035
           Summary: reload1.c:3766:41: error: ‘orig_dup[0]’ may be used
                    uninitialized in this function (for fr30, microblaze)
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: build, diagnostic
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: amylaar@gcc.gnu.org
            Blocks: 44756
            Target: fr30-elf, microblaze-elf, microblaze-linux


g++ -c   -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common 
-DHAVE_CONFIG_H -I. -I. -I../../../gcc/gcc -I../../../gcc/gcc/.
-I../../../gcc/gcc/../include -I../../../gcc/gcc/../libcpp/include 
-I../../../gcc/gcc/../libdecnumber -I../../../gcc/gcc/../libdecnumber/dpd
-I../libdecnumber -I../../../gcc/gcc/../libbacktrace   
../../../gcc/gcc/reload1.c -o reload1.o
../../../gcc/gcc/reload1.c: In function ‘void
calculate_elim_costs_all_insns()’:
../../../gcc/gcc/reload1.c:3766:41: error: ‘orig_dup[0]’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]
     *recog_data.dup_loc[i] = orig_dup[i];
                                         ^
../../../gcc/gcc/reload1.c:3642:7: note: ‘orig_dup[0]’ was declared here
   rtx orig_dup[MAX_RECOG_OPERANDS];
       ^
cc1plus: all warnings being treated as errors
make[2]: *** [reload1.o] Error 1


             reply	other threads:[~2012-10-23 14:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 14:23 amylaar at gcc dot gnu.org [this message]
2014-07-27 22:29 ` [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-27 22:31 ` 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@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).