From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13315 invoked by alias); 21 Sep 2017 23:59:45 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 13292 invoked by uid 89); 21 Sep 2017 23:59:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=57pm, 57PM X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-pg0-f44.google.com Received: from mail-pg0-f44.google.com (HELO mail-pg0-f44.google.com) (74.125.83.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Sep 2017 23:59:43 +0000 Received: by mail-pg0-f44.google.com with SMTP id i195so4368812pgd.9; Thu, 21 Sep 2017 16:59:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=zfq7RCnieLB6DTX5AtIVZ/Qtxb2d3UuWI0m8kLc1gyk=; b=mZUSlVrvMrLjUGeknY7XVPZOMR2yJGYg+NsPsVQlMqnTKKqA7jhEKPZ0MVcMAAXLzX 6+jAODNXV0ZBIbfGc6/74h0IlxL6sznKprhUtKM+vzxOzaRJEvLm4JxsI4Vtgy9qlJqR +XLRfhsbhQvsKWVaVtPO+3LJaSyMlpB3NFMIKoJsFCxMQ6iwCsBcl1mwNXqEthB+iock 5IK9TEIa68mvQiFP3xOlfdK3Dkr07+RDoLVd8dKkDxBdeVoknP871GRRY/EJ1vnkBBQy EXVI8qppQWGYnuq7GUXFpoFCVRfqclEWCORQWzhAS3w/8NsNTMkTb13hDKSyIhaF+4Fm ldCQ== X-Gm-Message-State: AHPjjUjPA4rvMDdDI24CSH3ys97Gxwcsnu4241Rn7iMz7T4JTe2VDEwP vF+xb391HKI9lWMovF0RMQY= X-Google-Smtp-Source: AOwi7QAZVzayp7rCJHrF51eqYXDQ0J0MPrp0BiyNXGvStQAALXoPSn45/CP2L12E4CvW8qHa0Xl7/A== X-Received: by 10.84.129.226 with SMTP id b89mr7152207plb.228.1506038381993; Thu, 21 Sep 2017 16:59:41 -0700 (PDT) Received: from bubble.grove.modra.org (CPE-58-175-73-248.czqe1.win.bigpond.net.au. [58.175.73.248]) by smtp.gmail.com with ESMTPSA id m21sm4541242pgn.60.2017.09.21.16.59.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Sep 2017 16:59:41 -0700 (PDT) Received: by bubble.grove.modra.org (Postfix, from userid 1000) id 1B0BCC23B2; Fri, 22 Sep 2017 09:29:37 +0930 (ACST) Date: Thu, 21 Sep 2017 23:59:00 -0000 From: Alan Modra To: Petr Ovtchenkov Cc: Joel Brobecker , Matthias Klose , Simon Marchi , Pedro Alves , Matt Rice , Fiodar Stryzhniou , Andreas Schwab , Binutils , GDB Subject: Re: meaning of "Automatic date update in version.in" commits Message-ID: <20170921235936.GB25070@bubble.grove.modra.org> References: <8740f2a7-1300-3116-f34b-5487a8cd8b2b@redhat.com> <20170921161743.3ddc6bb9@void-ptr.info> <20170921184615.6b1e5d44@void-ptr.info> <426b9fdf-a854-6d5f-b296-df71ad0c1561@ubuntu.com> <20170921192619.412ff148@void-ptr.info> <20170921163358.twez7kbewucjalwi@adacore.com> <20170921195153.4ed9f319@void-ptr.info> <20170921170031.czr6to24sarve2or@adacore.com> <20170921203857.06810b63@void-ptr.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170921203857.06810b63@void-ptr.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SW-Source: 2017-09/txt/msg00100.txt.bz2 On Thu, Sep 21, 2017 at 08:38:57PM +0300, Petr Ovtchenkov wrote: > On Thu, 21 Sep 2017 10:00:31 -0700 > Joel Brobecker wrote: > > > > It is evident for me. But in the discussion I see a lot of arguments, > > > that I treat as "date stamp is used as ABI compatibility marker". > > > > Then, I am in the same situation as Pedro. What problem are you trying > > to fix? > > Oops. Let's start from the begining. Far far away... > > 1. Explicit "Automatic date update in version.in" commits litter commits tree, > but useless. All required info already present in git. > [Thanks for Ian Lance Taylor for the background!] It isn't useless. People build binutils from a variety of sources, git, tarballs, distro sources, then report bugs. We want something that can easily identify the source they used. The bfd version plus date is usually good enough for that purpose. > Let's remove this "Automatic date update in version.in" commits. No. That won't happen unless we have something equivalent. And it must work *without* git. > 2. I see a lot of suggestions "Let's push date to SONAME, the date we > will take from ....". > > I trying to prevent such "solutions". Because it's not a solution, but > origin of another problems. The date is in the soname because people naturally expect shared libraries with the same soname to have compatible ABIs. During development, we could bump the bfd version on every ABI change, but that's just another thing contributors and maintainers would need to remember. It's much easier for all if the soname contains the date. Again, it's not perfect but is good enough. None of this is going to change just because you don't like a date stamp in the source. You do realize that a bisect uses a binary search, don't you? So doubling the number of commits just needs one extra build/test step on average. Yes, it would be nice if the automatic date stamp update didn't happen when the most recent commit was a date update.. -- Alan Modra Australia Development Lab, IBM