From: Arjan van de Ven <arjanv@fenrus.demon.nl>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: David Mansfield <lkml@dm.cobite.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Compile failure (gcc 2.96 bug?). 2.5.42 raid0.c
Date: 14 Oct 2002 23:11:55 +0200 [thread overview]
Message-ID: <1034629916.2937.25.camel@localhost.localdomain> (raw)
In-Reply-To: <1034628849.3038.23.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Mon, 2002-10-14 at 22:54, Arjan van de Ven wrote:
> On Mon, 2002-10-14 at 22:27, David Mansfield wrote:
> >
> > - sector_t x = block;
> > + volatile sector_t y = 0;
> > + sector_t x = block - y;
> > sector_div(x, (unsigned long)conf->smallest->size);
> > hash = conf->hash_table + x;
> > }
> this appears to be a bad code bug; do_div() requires the first argument
> to be an u64 and we cast it to unsigned long here....
ehm ignore me I'm blind
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-14 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 20:27 [BUG] Compile failure (gcc 2.96 bug?). 2.5.42 raid0.c David Mansfield
2002-10-14 20:54 ` Arjan van de Ven
2002-10-14 21:11 ` Arjan van de Ven [this message]
[not found] <540557597@toto.iv>
2002-10-15 0:18 ` Peter Chubb
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=1034629916.2937.25.camel@localhost.localdomain \
--to=arjanv@fenrus.demon.nl \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dm.cobite.com \
/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).