From owner-freebsd-arch@freebsd.org Thu Jun 9 20:38:37 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 3647BB703FF for ; Thu, 9 Jun 2016 20:38:37 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 F369B1DD3 for ; Thu, 9 Jun 2016 20:38:36 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-it0-x232.google.com with SMTP id a5so47978029ita.1 for ; Thu, 09 Jun 2016 13:38:36 -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:content-transfer-encoding :mime-version:subject:date:references; bh=gF9SbeJ6Zv3IpJyJlh+mkv9KT9RE3s38DBN8de0amS4=; b=dKfbL/aghMuJfdmpXE8mhsmxc7aFvZGDzpKbNhGbwCMIHcFNyYucmlu9SXQOVDI579 ZtkMSCmQtQPL8LKPS+PIgE4gp6HtmNeykaZTwaC13CZOotEL7lnB1mSRF/yk3koscPvK DuyL18TMdG97W5kVdsHwzZ+mNrUQzZ5CItY1z59QqsfLW8DVgPGPS1iIaySqR/EJC5W+ wezoyXa8RqbaPdSvopQqKVT/kiokVkqYThbEVIVaBCl8TeWnELY0c68+Nq7gS8zvqQ6e iitujdcTnJnD3SDT0aLJ0QPYxrp26iSDBHsG0bW07148myWMxZyYL3WE1FdXHkgy4ToY W0FA== 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 :content-transfer-encoding:mime-version:subject:date:references; bh=gF9SbeJ6Zv3IpJyJlh+mkv9KT9RE3s38DBN8de0amS4=; b=aInpS0kUoJmp3iHAqP3Agj+q9DN3TyQiG0OWshe0P6cNzzGKPl4wcfYBsdZ8SHmW0a 18yiS25H4HuN+PClsiIxgvsDDTTvli0dmYdYS/uIgyrAmppe3+3r9Kb2f+5ugh8S6xYE DdWkcQcboqkxp4lxjSjfvF3lVT9zoBjI9YWT3reFlrlx3mLFw/UQHpKgvTsOdurlbB7k LF4vqnoFGMpGZz741LVM3OrbLWv4hBla90VjvH0hu5XPhmq2Xh456sfj+gSe2hx887rb czCOdb45yeJ9J3RGECEJbJzVReMHn1dKHaY6ai5LKbe8n7iBafL+odDHEcHzeadijlAY KIKg== X-Gm-Message-State: ALyK8tIuw4LrYrY08oNwz/E/YCkw83waGqfooZu0l+U5qkqDZ86VCD0Z26kG92bT520ySQ== X-Received: by 10.36.68.88 with SMTP id o85mr20560070ita.39.1465504716453; Thu, 09 Jun 2016 13:38:36 -0700 (PDT) Received: from [10.65.211.198] ([137.122.64.8]) by smtp.gmail.com with ESMTPSA id u62sm14286065itd.10.2016.06.09.13.38.35 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 09 Jun 2016 13:38:36 -0700 (PDT) Sender: Justin Hibbits Cc: freebsd-arch@freebsd.org Message-Id: <51CA1453-0393-4D72-BAC6-053318B001E0@freebsd.org> From: Justin Hibbits To: Garance A Drosehn In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: PowerPC 64-bit time_t Date: Thu, 9 Jun 2016 16:38:34 -0400 References: <3FB65E20-0376-4041-86DE-F8CAB7F37314@freebsd.org> X-Mailer: Apple Mail (2.936) 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:38:37 -0000 On Jun 9, 2016, at 4:22 PM, Garance A Drosehn wrote: > On 9 Jun 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? > > I don't know if it would help to look at the changes done back when > sparc64 went to a 64-bit time_t. I did a lot of that work, but I'll > have to admit I remember almost nothing about the changes. > > -- > Garance Alistair Drosehn = drosih@rpi.edu > Senior Systems Programmer or gad@FreeBSD.org > Rensselaer Polytechnic Institute; Troy, NY; USA Thanks. The UPDATING.64BIT file you created for the upgrade path for sparc64 is an excellent source for the headaches involved with source based upgrades from 32-bit time_t to 64-bit. - Justin