[Bug c++/53356] [4.7/4.8 Regression] ICE in verify_gimple_stmt, at tree-cfg.c:4258

["quickhelp at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

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

tormen <quickhelp at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |quickhelp at gmail dot com

--- Comment #8 from tormen <quickhelp at gmail dot com> ---

Hmmm, I am not sure if I should reopen this bug or post a new one... but I ran
into the same error message, so I thought here is good.

And it says resolved in 4.7.1, but I am using 4.7.2 on a debian stable trying
to compile 3.9.6 linux kernel and I ran into the same error:

  CC [M]  fs/ntfs/quota.o
  CC [M]  fs/ntfs/usnjrnl.o
  LD [M]  fs/ntfs/ntfs.o
  LD      fs/ocfs2/built-in.o
  CC [M]  fs/ocfs2/alloc.o
/tmp/dl/linux-3.9.6/fs/ocfs2/alloc.c: In function âocfs2_merge_rec_rightâ:
/tmp/dl/linux-3.9.6/fs/ocfs2/alloc.c:3347:12: internal compiler error: in
verify_gimple_stmt, at tree-cfg.c:4258
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[6]: *** [fs/ocfs2/alloc.o] Error 1
make[5]: *** [fs/ocfs2] Error 2
make[4]: *** [fs] Error 2
make[3]: *** [sub-make] Error 2
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/tmp/dl/linux-3.9.6/debian/build/build_amd64_none_amd64'
make[1]: *** [debian/stamps/build_amd64_none_amd64_plain] Error 2
make[1]: Leaving directory `/tmp/dl/linux-3.9.6'
make: *** [binary-arch_amd64_none_amd64_real] Error 2


The steps I did:
   apt-get install build-essential fakeroot

   apt-get build-dep linux-headers-3.9-0.bpo.1-amd6
   apt-get source linux-headers-3.9-0.bpo.1-amd64

   cd linux-3.9.6

   fakeroot make -f debian/rules.gen binary-arch_amd64

I am not sure if this is the right place to post this... but then I thought
that this shouldn't be a debian specific problem... or?

Any ideas ?