From: Robert Love <rml@tech9.net>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: gcc-bugs@gcc.gnu.org, linux-kernel@vger.kernel.org
Subject: Re: 3.0.2 breaks linux-2.4.13-ac8 in tcp.c
Date: 06 Nov 2001 00:24:18 -0500 [thread overview]
Message-ID: <1005024259.1376.4.camel@phantasy> (raw)
In-Reply-To: <200111060513.fA65DqZ26051@vegae.deep.net>
In-Reply-To: <200111060513.fA65DqZ26051@vegae.deep.net>
On Tue, 2001-11-06 at 00:13, Samium Gromoff wrote:
> well, not too much to add, maybe except that the RAM is ok and CPU is not
> OC`ed...
> [...]
> tcp.c: In function `tcp_close':
> tcp.c:1978: Internal compiler error in rtx_equal_for_memref_p, at alias.c:1121
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
This is the GCC team's worry -- it is an internal GCC bug. Send them
the compile log and the source file in question.
See http://www.gnu.org/software/gcc/bugs.html
Robert Love
next prev parent reply other threads:[~2001-11-06 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 5:13 3.0.2 breaks linux-2.4.13-ac8 in tcp.c Samium Gromoff
2001-11-06 5:24 ` Robert Love [this message]
2001-11-15 13:30 ` Samium Gromoff
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=1005024259.1376.4.camel@phantasy \
--to=rml@tech9.net \
--cc=_deepfire@mail.ru \
--cc=gcc-bugs@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.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