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] New: [4.8/4.9/4.10 Regression] -fcompare-debug errors while building Linux kernel.
Date: Sat, 26 Jul 2014 20:03:00 -0000 [thread overview]
Message-ID: <bug-61923-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61923
Bug ID: 61923
Summary: [4.8/4.9/4.10 Regression] -fcompare-debug errors while
building Linux kernel.
Product: gcc
Version: 4.8.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: trippels at gcc dot gnu.org
Building the Linux kernel with "GCC_COMPARE_DEBUG=1 make" hits several
failures.
markus@x4 tmp % cat inode.i
typedef struct
{
struct
{
struct
{
char head;
} tickets;
};
} arch_spinlock_t;
struct ext4_map_blocks
{
int m_lblk;
int m_len;
int m_flags;
};
int ext4_da_map_blocks_ei_0;
void fn1 (int p1, struct ext4_map_blocks *p2)
{
int ret;
if (p2->m_flags)
{
ext4_da_map_blocks_ei_0++;
arch_spinlock_t *lock;
switch (sizeof *&lock->tickets.head)
case 1:
asm("" : "+m"(*&lock->tickets.head) : ""(0));
__asm__("");
ret = 0;
}
fn2 (p2->m_lblk, p2->m_len);
}
markus@x4 tmp % gcc -c -O2 -fcompare-debug inode.i --save-temps
gcc: error: inode.i: -fcompare-debug failure (length)
markus@x4 tmp % diff -u inode.gkd inode.gk.gkd
--- inode.gkd 2014-07-26 22:01:20.578062879 +0200
+++ inode.gk.gkd 2014-07-26 22:01:20.598062450 +0200
@@ -82,7 +82,7 @@
(expr_list:REG_EQUIV (mem:SI (plus:DI (reg/v/f:DI 0 ax [orig:90 p2 ]
[90])
(const_int 4 [0x4])) [ p2_3(D)->m_len+0 S4 A32])
(nil)))
-(insn:TI# 0 0 4 (set (reg:SI 5 di)
+(insn# 0 0 4 (set (reg:SI 5 di)
(mem:SI (reg/v/f:DI 0 ax [orig:90 p2 ] [90]) [ p2_3(D)->m_lblk+0 S4
A32])) inode.i:31# {*movsi_internal}
(expr_list:REG_DEAD (reg/v/f:DI 0 ax [orig:90 p2 ] [90])
(nil)))
next reply other threads:[~2014-07-26 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 20:03 trippels at gcc dot gnu.org [this message]
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
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@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).