public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/63404] New: gcc 5 miscompiles linux block layer
Date: Mon, 29 Sep 2014 04:20:00 -0000 [thread overview]
Message-ID: <bug-63404-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63404
Bug ID: 63404
Summary: gcc 5 miscompiles linux block layer
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: andi-gcc at firstfloor dot org
When I boot a current Linux mainline kernel compiled with mainline gcc
and the section fix patch applied I always get a crash at boot in the block
layer.
gcc version 5.0.0 20140926 (experimental) (GCC)
1.318801] EXT4-fs (sda1): write access will be enabled during recovery
[ 1.367592] ------------[ cut here ]------------
[ 1.369061] kernel BUG at /home/andi/lsrc/linux/block/blk-flush2.c:80!
[ 1.370910] invalid opcode: 0000 [#1] SMP
I narrowed it down to one function. When only the function is compiled with gcc
4.9 the kernel boots.
Attach is a test case with only the function.
It doesn't quite run by itself yet, so the code has to be examined.
next reply other threads:[~2014-09-29 4:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 4:20 andi-gcc at firstfloor dot org [this message]
2014-09-29 4:26 ` [Bug middle-end/63404] " andi-gcc at firstfloor dot org
2014-09-29 4:57 ` [Bug target/63404] " andi-gcc at firstfloor dot org
2014-09-29 8:29 ` [Bug target/63404] [5 Regression] " trippels at gcc dot gnu.org
2014-09-29 10:49 ` jiwang at gcc dot gnu.org
2014-09-29 11:14 ` jiwang at gcc dot gnu.org
2014-09-29 18:46 ` pthaugen at gcc dot gnu.org
2014-09-29 18:48 ` jiwang at gcc dot gnu.org
2014-09-29 18:50 ` jiwang at gcc dot gnu.org
2014-09-29 21:03 ` dominiq at lps dot ens.fr
2014-10-01 20:45 ` pthaugen at gcc dot gnu.org
2014-10-08 4:42 ` pinskia at gcc dot gnu.org
2014-10-10 15:56 ` rth at gcc dot gnu.org
2014-10-17 12:14 ` trippels at gcc dot gnu.org
2014-11-07 15:55 ` jiwang 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-63404-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).