From owner-freebsd-arch Fri Oct 26 9:45:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id D5B4437B408 for ; Fri, 26 Oct 2001 09:45:46 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9QGj8M03688; Fri, 26 Oct 2001 18:45:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: Julian Elischer , Terry Lambert , Peter Wemm , arch@FreeBSD.ORG Subject: Re: 64 bit times revisited.. In-Reply-To: Your message of "Fri, 26 Oct 2001 11:42:49 CDT." <20011026114249.E15052@elvis.mu.org> Date: Fri, 26 Oct 2001 18:45:08 +0200 Message-ID: <3686.1004114708@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011026114249.E15052@elvis.mu.org>, Alfred Perlstein writes: >> And have you considered that there may be other and stronger >> requirements than make(1) and that multi-cpu, multi-threaded systems >> may push the envelope ? >> >> Solving the problem means going for a timestamp which can resolve >> any conceiveable CPU frequencies for all relevant future. > >I guess I should have more in depth knowledge of these systems by >now, but what's wrong with having the in-core being a full >64/128/whatever bits while the on disk itself doesn't? Because applications in core write files on disk ? :-) I'm merely advocating solving the problem and not hacking around it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message