public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/61923] [4.8/4.9/4.10 Regression] -fcompare-debug errors while building Linux kernel.
Date: Tue, 29 Jul 2014 06:54:00 -0000	[thread overview]
Message-ID: <bug-61923-4-aGfVFtERjn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61923-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61923

--- Comment #3 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Created attachment 33200
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33200&action=edit
original testcase

The issue is more visible with the original attached testcase:

markus@x4 linux % diff -u inode.gkd inode.gk.gkd
--- inode.gkd   2014-07-29 08:52:00.453657959 +0200
+++ inode.gk.gkd        2014-07-29 08:52:01.636965368 +0200
@@ -4270,15 +4270,6 @@
             (nil))))
 (code_label 158 0 0 16 158 "" [1 uses])
 (note# 0 0 [bb 16] NOTE_INSN_BASIC_BLOCK)
-(insn:TI# 0 0 16 (set (reg:SI 37 r8)
-        (const_int 2 [0x2])) fs/ext4/inode.c:1632# {*movsi_internal}
-     (nil))
-(insn# 0 0 16 (set (reg:DI 2 cx)
-        (const_int -1 [0xffffffffffffffff])) fs/ext4/inode.c:1632#
{*movdi_internal}
-     (nil))
-(insn# 0 0 16 (set (reg:DI 5 di)
-        (reg/v/f:DI 44 r15 [orig:208 inode ] [208])) fs/ext4/inode.c:1632#
{*movdi_internal}
-     (nil))
 (insn:TI# 0 0 16 (set (reg:SI 1 dx)
         (mem/c:SI (plus:DI (reg/f:DI 7 sp)
                 (const_int 28 [0x1c])) [ map.m_len+0 S4 A32]))
fs/ext4/inode.c:1632# {*movsi_internal}
@@ -4287,6 +4278,15 @@
         (mem/c:SI (plus:DI (reg/f:DI 7 sp)
                 (const_int 24 [0x18])) [ map.m_lblk+0 S4 A64]))
fs/ext4/inode.c:1632# {*movsi_internal}
      (nil))
+(insn# 0 0 16 (set (reg:SI 37 r8)
+        (const_int 2 [0x2])) fs/ext4/inode.c:1632# {*movsi_internal}
+     (nil))
+(insn:TI# 0 0 16 (set (reg:DI 2 cx)
+        (const_int -1 [0xffffffffffffffff])) fs/ext4/inode.c:1632#
{*movdi_internal}
+     (nil))
+(insn# 0 0 16 (set (reg:DI 5 di)
+        (reg/v/f:DI 44 r15 [orig:208 inode ] [208])) fs/ext4/inode.c:1632#
{*movdi_internal}
+     (nil))
 (call_insn:TI# 0 0 16 (set (reg:SI 0 ax)
         (call (mem:QI (symbol_ref:DI ("ext4_es_insert_extent") [flags 0x41] 
<function_decl # ext4_es_insert_extent>) [ ext4_es_insert_extent S1 A8])
             (const_int 0 [0]))) fs/ext4/inode.c:1632# {*call_value}


  parent reply	other threads:[~2014-07-29  6:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26 20:03 [Bug debug/61923] New: " trippels at gcc dot gnu.org
2014-07-28  8:16 ` [Bug debug/61923] " rguenth at gcc dot gnu.org
2014-07-28  8:18 ` pinskia at gcc dot gnu.org
2014-07-29  6:54 ` trippels at gcc dot gnu.org [this message]
2014-08-01 11:44 ` jakub at gcc dot gnu.org
2014-08-06  2:00 ` vmakarov at gcc dot gnu.org
2014-08-06 15:36 ` vmakarov at gcc dot gnu.org
2014-08-06 15:41 ` vmakarov at gcc dot gnu.org
2014-08-06 16:00 ` trippels at gcc dot gnu.org
2014-09-08 19:07 ` [Bug debug/61923] [4.8 " jakub at gcc dot gnu.org
2014-09-08 19:17 ` jakub 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-61923-4-aGfVFtERjn@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).