From owner-freebsd-arch@freebsd.org Thu Jun 9 20:09:42 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F12F5B70C77 for ; Thu, 9 Jun 2016 20:09:42 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B950C19A9 for ; Thu, 9 Jun 2016 20:09:42 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-it0-x22e.google.com with SMTP id h190so44341330ith.1 for ; Thu, 09 Jun 2016 13:09:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:cc:message-id:from:to:in-reply-to:mime-version:subject:date :references; bh=o1k4Dszd1fEJg/HF0G4HsxcOFl50zqkuC4UqGvAAWYM=; b=qsuG0/vaqGyee8nsHlBrDWOmvAfDEgNnyykAYnovGMfJbL3vwXCVIxDhcEngqlaZE3 qh4rAhilIQkmTh6KxzWko7tUNRJ7d4hkMZZESYJrKFD9uuXkK37/xnV9MyFbAiD0NRya /dFmRCd2o3SlWl1H8ZaAkO828MlVuneuQ0xLqp5RjWA/A03zmX4HnzaJFnP3bL5m8yti giLPaqXd591iHPQGybrSSJdGwFhVYJVek9b1BwscBBKXB/2jTsEQdzGl3oEvrvZjFlGv 2yp7X+o+vH5ql/uuhfFe9IdzPfMSd+6Wp64f9knSkG+85QdPkLgq6yzf4RwT4siJs9rC 0WhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:cc:message-id:from:to:in-reply-to :mime-version:subject:date:references; bh=o1k4Dszd1fEJg/HF0G4HsxcOFl50zqkuC4UqGvAAWYM=; b=PZafc4k2NjnKHeJN1HvyuikXU/W59VNY89tnwq7qgAzNnxikmxl09tQke31vAYQDTc sKmzQxqUmDmIneZR3kAHbdkRbrYEKiF2560NnyKgkzTviVgaE+sJvzhVdNEPcH9ZioZQ Y01q/cVL/QPOtoHcy9WS1MKG54iwMk9uAbiAJ9a6Tn9QsbH8jhxvHL8GdCXBWZPNaHRd 1wpdc0kc6pM2vc0DcN+ggj0ZExD6bOnN/aJPPFpw162l8w2J7MTFHiVdtAE1v8L8wmKN qNGUCaTyY2b8Qvi/1FInX0RapIYPMsxmHqaYM7zch69q3qr0GZ7FPMl81+qpGL3KdcwI +U9w== X-Gm-Message-State: ALyK8tIJ6o5dqKfshzCfmuqbYe+/XAAlu3XYn5C5l4KbunUGeLGtFJC/OmvKZH4B1nFlxA== X-Received: by 10.36.55.138 with SMTP id r132mr25533610itr.73.1465502982162; Thu, 09 Jun 2016 13:09:42 -0700 (PDT) Received: from [10.65.211.198] ([137.122.64.8]) by smtp.gmail.com with ESMTPSA id 142sm3916359itk.12.2016.06.09.13.09.41 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 09 Jun 2016 13:09:41 -0700 (PDT) Sender: Justin Hibbits Cc: FreeBSD Arch Message-Id: <8CD57763-E623-480F-A2E4-3145A3C22F86@freebsd.org> From: Justin Hibbits To: Doug Rabson In-Reply-To: Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: PowerPC 64-bit time_t Date: Thu, 9 Jun 2016 16:09:40 -0400 References: <3FB65E20-0376-4041-86DE-F8CAB7F37314@freebsd.org> X-Mailer: Apple Mail (2.936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2016 20:09:43 -0000 This would only be needed if syscall ABI compatibility is required, right? Considering the current support state and userbase of powerpc, a simple binary option of 32 vs 64 should be sufficient, I believe. For i386 it's a different story, since it's much more widely used (and tier1) so backwards compatibility is 100% necessary. - Justin On Jun 9, 2016, at 3:37 PM, Doug Rabson wrote: > Well you have to maintain the kernel's syscall ABI, which basically > means adding new syscalls for anything which is affected. > > On 9 June 2016 at 13:41, Justin Hibbits wrote: > At the devsummit earlier today I mentioned for FreeBSD 12 wanting 64- > bit time_t across the board. It was pointed out that the only ones > with 32-bit time_t are i386 and powerpc (32-bit). I've made the > changes necessary for at least kernel (world is still building right > now), but it's obviously an ABI and KBI incompatible change. > Addressing KBI is a nonissue, as that's expected to break at major > releases. ABI is another issue. I'm unsure how to properly address > ABI breakage -- bumping libc's .so version, or reversion all symbols > that use something with time_t, or something else. If I can address > it before the code freeze, it could be done for FreeBSD 11, which > leaves about 6 hours from now. > > Any thoughts? > > - Justin > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch- > unsubscribe@freebsd.org" >