public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "maxdeliso at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50850] New: verify_ssa failed
Date: Mon, 24 Oct 2011 12:03:00 -0000	[thread overview]
Message-ID: <bug-50850-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50850
           Summary: verify_ssa failed
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: maxdeliso@gmail.com


Created attachment 25589
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25589
the preprocessed gfs2 file.c with triggers the bug

Bug Report
    Date: Mon Oct 24 07:56:29 EDT 2011
System Info
    gcc version: 4.7.0 20111024 (experimental) (GCC) 
    uname -a: Linux koplaix 3.1.0-rc10+ #3 SMP Sat Oct 22 19:22:40 EDT 2011
x86_64 GNU/Linux

Bug Info
    compiler output: 
      fs/gfs2/file.c: In function ‘gfs2_set_inode_flags’:
      fs/gfs2/file.c:172:6: error: definition in block 3 does not dominate use
in block 2
      for SSA_NAME: .MEM_32 in statement:
      .MEM_32 = PHI <.MEM_32(2)>
      PHI argument
      .MEM_32
      for PHI node
      .MEM_32 = PHI <.MEM_32(2)>
      fs/gfs2/file.c:172:6: internal compiler error: verify_ssa failed
      Please submit a full bug report,
      with preprocessed source if appropriate.
      See <http://gcc.gnu.org/bugs.html> for instructions.
    on git kernel commit: c3b92c8787367a8bb53d57d9789b558f1295cc96
    triggering commandline:
      gcc -Wp,-MD,fs/gfs2/.file.o.d  -nostdinc -isystem
/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.7.0/include
-I/home/maxx/src/linux-2.6/arch/x86/include -Iarch/x86/include/generated
-Iinclude  -include /home/maxx/src/linux-2.6/include/linux/kconfig.h
-D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -fno-common -Werror-implicit-function-declaration
-Wno-format-security -fno-delete-null-pointer-checks -Os -m64 -march=core2
-mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args
-DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1
-DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables
-mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=2048
-fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer
-Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow
-fconserve-stack -DCC_HAVE_ASM_GOTO -Ifs/gfs2  -DMODULE  -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(file)"  -D"KBUILD_MODNAME=KBUILD_STR(gfs2)" -c -o
fs/gfs2/file.o fs/gfs2/file.c
    (preprocessed file attached as file.i)


             reply	other threads:[~2011-10-24 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 12:03 maxdeliso at gmail dot com [this message]
2011-10-24 13:57 ` [Bug tree-optimization/50850] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-10-24 17:57 ` belyshev at depni dot sinp.msu.ru
2011-10-27  0:48 ` maxdeliso at gmail dot com
2011-10-27  7:22 ` belyshev at depni dot sinp.msu.ru

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-50850-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).