From owner-svn-src-all@freebsd.org Fri May 6 09:40:07 2016 Return-Path: Delivered-To: svn-src-all@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 01AD6B2F464; Fri, 6 May 2016 09:40:06 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail107.syd.optusnet.com.au (mail107.syd.optusnet.com.au [211.29.132.53]) by mx1.freebsd.org (Postfix) with ESMTP id AD0B112C3; Fri, 6 May 2016 09:40:06 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from c122-106-149-109.carlnfd1.nsw.optusnet.com.au (c122-106-149-109.carlnfd1.nsw.optusnet.com.au [122.106.149.109]) by mail107.syd.optusnet.com.au (Postfix) with ESMTPS id 175E4D463FF; Fri, 6 May 2016 19:14:05 +1000 (AEST) Date: Fri, 6 May 2016 19:14:02 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Alan Somers cc: John Baldwin , "src-committers@freebsd.org" , "svn-src-all@freebsd.org" , "svn-src-head@freebsd.org" , Justin Gibbs Subject: Re: svn commit: r299090 - in head: etc/mtree include lib/libbluetooth sbin/hastd share/man/man3 sys/dev/xen/blkback sys/kern sys/net sys/sys tests/sys tests/sys/sys usr.sbin/bluetooth/hccontrol In-Reply-To: Message-ID: <20160506184035.E1151@besplex.bde.org> References: <201605042234.u44MYBMX054443@repo.freebsd.org> <2368543.Vvp613SNcD@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=TuMb/2jh c=1 sm=1 tr=0 a=R/f3m204ZbWUO/0rwPSMPw==:117 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=6I5d2MoRAAAA:8 a=LudcZlNRvWZrs-_xYP4A:9 a=CjuIK1q_8ugA:10 a=IjZwj45LgO3ly-622nXo:22 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 09:40:07 -0000 On Thu, 5 May 2016, Alan Somers wrote: > On Thu, May 5, 2016 at 10:31 AM, John Baldwin wrote: > >> On Wednesday, May 04, 2016 10:34:11 PM Alan Somers wrote: >>> ... >>> Log: >>> Improve performance and functionality of the bitstring(3) api >> ... >> Doesn't switching from bytes to longs break the ABI? That is, setting bit >> 9 >> ... >> Is the API is so little used we don't care? > > The API isn't used in any shared libraries, so the only risk would be if > it's used in a user application where the user's build system doesn't check > for changes in system libraries, and the user upgrades FreeBSD without > doing a clean build of his application, right? Am I missing any other > scenarios? Do we need to warn users with a line in UPDATING or something? All scenarios where the binary format is used for data layouts that live for more than a few microseconds. Little things like file systems and networks. > This is similar to an upgrade of the C++ compiler. C++ objects built by > different minor versions of the compiler aren't guaranteed to be compatible. So C++ is also unsuitable for little things like file systems and networks :-). Bruce