From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Arch Mailing List <linux-arch@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH REVISED] Avoid overflows in kernel/time.c
Date: Fri, 14 Dec 2007 09:58:41 -0800 [thread overview]
Message-ID: <4762C451.7020601@zytor.com> (raw)
In-Reply-To: <20071214081033.GA17598@uranus.ravnborg.org>
Sam Ravnborg wrote:
>
> I understood that bc is unreliable.
> How about creating a small .c program that does to necessary computation
> and integrate it in the build process.
> It should be much cleaner than this approach.
>
You'd have to include an extended-precision library in said C program.
-hpa
prev parent reply other threads:[~2007-12-14 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 1:13 [PATCH REVISED] Avoid overflows in kernel/time.c H. Peter Anvin
2007-12-14 8:10 ` Sam Ravnborg
2007-12-14 17:58 ` H. Peter Anvin [this message]
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=4762C451.7020601@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sam@ravnborg.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).