public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/21840] Linux 2.6.11.1.11: drivers/char/keyboard.c:619: internal compiler error: Segmentation fault
Date: Tue, 31 May 2005 14:45:00 -0000 [thread overview]
Message-ID: <20050531144025.3423.qmail@sourceware.org> (raw)
In-Reply-To: <20050531135612.21840.mclinden@informed.net>
------- Additional Comments From pluto at agmk dot net 2005-05-31 14:40 -------
[ PR21839, PR21840 ]
Sean, Do the sigsegvs occur in random places during kernel build?
If yes then You must check other RAM chips. Memtest86 is not enough
to be 100% sure. You should also try the parallel kernel build (eg. `make -j8`).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21840
next prev parent reply other threads:[~2005-05-31 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 13:57 [Bug c/21840] New: " mclinden at informed dot net
2005-05-31 14:05 ` [Bug middle-end/21840] " pinskia at gcc dot gnu dot org
2005-05-31 14:35 ` mclinden at informed dot net
2005-05-31 14:45 ` pluto at agmk dot net [this message]
2005-05-31 14:57 ` pinskia at gcc dot gnu dot org
2005-05-31 14:59 ` [Bug middle-end/21840] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-05-31 15:10 ` pinskia at gcc dot gnu dot org
2005-05-31 15:41 ` dberlin at gcc dot gnu dot org
2005-06-16 23:53 ` pluto at agmk dot net
2005-07-12 6:54 ` [Bug middle-end/21840] [4.1 Regression] ICE while building Linux kernel (seg fault), missing cast pinskia at gcc dot gnu dot org
2005-07-12 17:00 ` pinskia at gcc dot gnu dot org
2005-07-13 2:22 ` pinskia at gcc dot gnu dot org
2005-07-13 2:33 ` cvs-commit at gcc dot gnu dot org
2005-07-13 2:33 ` pinskia 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=20050531144025.3423.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).