public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45312] GCC 4.4.4 miscompiles (?) the Linux kernel, makes kernel unusable
Date: Wed, 18 Aug 2010 08:55:00 -0000 [thread overview]
Message-ID: <20100818085512.20520.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45312-5637@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from jakub at gcc dot gnu dot org 2010-08-18 08:55 -------
Doing binary search shouldn't be too hard, just build two separate kernel
trees, one with the problematic patch applied, one without, with make V=1
output put into some log file in each case.
Then just start with the final link line and replace half of the
objects/libraries there with matching objects/libraries from the second build
and vice versa, test that kernel and depending on the results continue
narrowing it down to half of the object files/libraries etc., repeat until you
have e.g. working kernel with all objects with the patch applied except one (or
non-working kernel with all objects without the patch applied except one).
Or, if you suspect particular object files, try to change just those
immediately.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45312
next prev parent reply other threads:[~2010-08-18 8:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 18:12 [Bug c/45312] New: " t dot artem at mailcity dot com
2010-08-17 18:24 ` [Bug c/45312] " jakub at gcc dot gnu dot org
2010-08-17 19:08 ` jakub at gcc dot gnu dot org
2010-08-18 4:05 ` t dot artem at mailcity dot com
2010-08-18 4:41 ` [Bug middle-end/45312] " belyshev at depni dot sinp dot msu dot ru
2010-08-18 5:12 ` t dot artem at mailcity dot com
2010-08-18 8:55 ` jakub at gcc dot gnu dot org [this message]
2010-08-18 20:00 ` t dot artem at mailcity dot com
2010-08-23 16:01 ` hpa at zytor dot com
2010-08-24 10:19 ` jakub at gcc dot gnu dot org
2010-08-24 10:31 ` [Bug middle-end/45312] [4.4 Regression] GCC 4.4.4 miscompiles the Linux kernel jakub at gcc dot gnu dot org
2010-08-24 10:43 ` jakub at gcc dot gnu dot org
2010-09-01 18:06 ` vmakarov at redhat dot com
2010-09-01 18:32 ` jakub at gcc dot gnu dot org
2010-09-03 18:30 ` uweigand at gcc dot gnu dot org
2010-09-03 20:45 ` vmakarov at redhat dot com
2010-09-06 16:58 ` uweigand at gcc dot gnu dot org
2010-09-07 18:03 ` vmakarov at redhat dot com
2010-09-07 19:18 ` uweigand at gcc dot gnu dot org
2010-09-09 18:36 ` vmakarov at gcc dot gnu dot org
2010-09-09 18:37 ` vmakarov at gcc dot gnu dot org
2010-09-09 18:38 ` vmakarov at gcc dot gnu dot org
2010-09-13 17:54 ` belyshev at depni dot sinp dot msu dot ru
2010-09-14 15:46 ` vmakarov at redhat dot com
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=20100818085512.20520.qmail@sourceware.org \
--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).