From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: gcc2.96 + prerelease BUG at inode.c:372
Date: 3 Jan 2001 15:40:23 -0800 [thread overview]
Message-ID: <930d97$83s$1@penguin.transmeta.com> (raw)
In-Reply-To: <200101031919.f03JJQU13197@interno.emmenet.it>
In article <200101031919.f03JJQU13197@interno.emmenet.it>,
Diego Liziero <pmcq@interno.emmenet.it> wrote:
>
>->1: The sound module for my mad16 based card plays the bytes swapped
> (the same module recompiled with egcs-2.91.66 works fine).
Could you try to figure this one out a bit more? This sounds like a real
compiler issue, whether it is because egcs just happens to get the right
result for bogus kernel source, of whether gcc-2.96 has problems..
>->2: after two day under heavy load I've got the following BUG:
> (I don't know if it's related to the compiler, that's why I'm reporting
> this.)
Unrelated. This one is a known bug that hits if you are a bit unlucky
with a race on deleting the pages from the inode page-lists. Fixed in
the current prerelease patches on ftp.kernel.org.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-03 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 19:19 gcc2.96 + prerelease BUG at inode.c:372 Diego Liziero
2001-01-03 20:07 ` Daniel Phillips
2001-01-03 23:40 ` Linus Torvalds [this message]
[not found] <200101032340.PAA08324@penguin.transmeta.com>
2001-01-04 1:34 ` Diego Liziero
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='930d97$83s$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.