public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/31944] New: Endless loop while building a 64-bit 2.6.20 kernel Date: Tue, 15 May 2007 23:14:00 -0000 [thread overview] Message-ID: <bug-31944-8932@http.gcc.gnu.org/bugzilla/> (raw) The file fs/ocfs2/dlm/dlmmaster.c from the 2.6.20 kernel triggers an endless loop in gcc 4.1 built for the hppa64-linux-gnu target. It occurs at -O2, but not at -O1 or -O0. Also specifying -fno-cse-follow-jumps workaround the problem. Thanks to Randolph Chung we have a reduced testcase: struct bug { int type; }; static void stuck(struct bug *mle, void *res) { if (mle->type == 1) { if (res == 0) asm volatile("nop"); } else if (mle->type == 0) { if (res == 0) { asm volatile("nop" : : "i" (0)); } } } void foo(void) { stuck(0, 0); } void bar(void) { stuck(0, 0); } And some infos about the compiler used: Using built-in specs. Target: hppa64-linux-gnu Configured with: ../src/configure --enable-languages=c --prefix=/usr --libexecdir=/usr/lib --disable-shared --disable-nls --disable-threads --disable-libffi --disable-libgomp --disable-libmudflap --disable-libssp --with-as=/usr/bin/hppa64-linux-gnu-as --with-ld=/usr/bin/hppa64-linux-gnu-ld --includedir=/usr/hppa64-linux-gnu/include --host=hppa-linux-gnu --build=hppa-linux-gnu --target=hppa64-linux-gnu Thread model: single gcc version 4.1.3 20070429 (prerelease) (Debian 4.1.2-6) -- Summary: Endless loop while building a 64-bit 2.6.20 kernel Product: gcc Version: 4.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: aurelien at aurel32 dot net GCC build triplet: hppa1.1-linux-gnu GCC host triplet: hppa1.1-linux-gnu GCC target triplet: hppa64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31944
next reply other threads:[~2007-05-15 23:14 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-15 23:14 aurelien at aurel32 dot net [this message] 2007-05-16 10:08 ` [Bug rtl-optimization/31944] " aurelien at aurel32 dot net 2007-05-17 2:55 ` danglin at gcc dot gnu dot org 2007-05-20 16:38 ` danglin at gcc dot gnu dot org 2007-05-20 17:15 ` danglin at gcc dot gnu dot org 2007-05-20 18:02 ` danglin at gcc dot gnu dot org 2007-05-20 20:31 ` danglin at gcc dot gnu dot org 2007-12-05 20:33 ` [Bug rtl-optimization/31944] [4.1/4.2/4.3 Regression] " danglin at gcc dot gnu dot org 2007-12-05 21:51 ` rguenth at gcc dot gnu dot org 2007-12-05 22:29 ` steven at gcc dot gnu dot org 2007-12-15 23:17 ` dave at hiauly1 dot hia dot nrc dot ca 2007-12-26 1:34 ` pinskia at gcc dot gnu dot org 2008-01-01 2:11 ` [Bug rtl-optimization/31944] [4.1/4.2 " danglin at gcc dot gnu dot org 2008-01-01 17:00 ` rguenther at suse dot de 2008-01-01 21:34 ` [Bug rtl-optimization/31944] [4.1/4.2/4.3 " danglin at gcc dot gnu dot org 2008-01-08 16:18 ` steven at gcc dot gnu dot org 2008-01-08 16:45 ` rguenth at gcc dot gnu dot org 2008-01-09 15:54 ` rguenth at gcc dot gnu dot org 2008-01-09 19:23 ` steven at gcc dot gnu dot org 2008-01-10 1:00 ` steven at gcc dot gnu dot org 2008-01-10 23:59 ` janis at gcc dot gnu dot org 2008-01-11 1:02 ` steven at gcc dot gnu dot org 2008-01-11 1:03 ` janis at gcc dot gnu dot org 2008-01-11 1:08 ` steven at gcc dot gnu dot org 2008-01-11 1:24 ` steven at gcc dot gnu dot org 2008-01-11 19:13 ` ebotcazou at gcc dot gnu dot org 2008-01-11 19:46 ` ebotcazou at gcc dot gnu dot org 2008-01-11 21:52 ` dave at hiauly1 dot hia dot nrc dot ca 2008-01-12 4:00 ` steven at gcc dot gnu dot org 2008-01-12 8:36 ` ebotcazou at gcc dot gnu dot org 2008-01-14 12:36 ` ebotcazou at gcc dot gnu dot org 2008-01-14 12:46 ` ebotcazou at gcc dot gnu dot org 2008-01-14 12:46 ` ebotcazou at gcc dot gnu dot org 2008-01-14 12:48 ` ebotcazou at gcc dot gnu dot 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-31944-8932@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: linkBe 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).