From: Josh McKinney <forming@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.9: GCC 3.0 problem in "acct.c"
Date: Wed, 22 Aug 2001 23:05:39 -0500 [thread overview]
Message-ID: <20010822230539.A5013@home.com> (raw)
In-Reply-To: <200108222251.BAA04797@ares.sot.com>
In-Reply-To: <200108222251.BAA04797@ares.sot.com>
On approximately Thu, Aug 23, 2001 at 01:51:33AM +0300, Santeri Kannisto wrote:
> Except that a similar problem with capi existed allready with gcc 3.0 +
> kernels 2.4.*, and that problem was reported to gcc people multiple
> times. But it is still broken in gcc 3.0.1:
>
> bp2.c:414: warning: `sbp2_host_info_lock' defined but not used
> capi.c: In function `capi_ioctl':
> capi.c:1031: Unrecognizable insn:
> (insn/i 1675 3103 3100 (parallel[ capi.c:1031: Internal error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>
> So, does anyone have any ideas? That problem is critical because
> it makes ISDN (capi 2) unusable with kernels 2.4.* + gcc 3.0.*
>
> All other things seem to function pretty well with 2.4.9 + 3.0.1.
I get the same sort of Unrecognizable insn: error in signal.c with my setup.
This is true today with the latest cvs gcc.
Josh
next prev parent reply other threads:[~2001-08-23 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 22:51 2.4.9: GCC 3.0 problem in "acct.c" Santeri Kannisto
2001-08-23 4:05 ` Josh McKinney [this message]
[not found] <no.id>
2001-08-18 22:21 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-08-18 18:09 peter k.
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=20010822230539.A5013@home.com \
--to=forming@home.com \
--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;
as well as URLs for NNTP newsgroup(s).