From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: [PATCH] gnu: gcc-4.9: Update to 4.9.4. Date: Mon, 24 Oct 2016 16:07:24 -0400 Message-ID: <87shrla4ub.fsf@netris.org> References: <7t4m42uque.fsf@gmail.com> <20161024131638.GA22075@jasmine> <7tfunlu86a.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bylXE-00030a-7J for guix-devel@gnu.org; Mon, 24 Oct 2016 16:07:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bylXB-0000Sh-23 for guix-devel@gnu.org; Mon, 24 Oct 2016 16:07:52 -0400 Received: from world.peace.net ([50.252.239.5]:36686) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bylXA-0000OE-U3 for guix-devel@gnu.org; Mon, 24 Oct 2016 16:07:48 -0400 In-Reply-To: <7tfunlu86a.fsf@gmail.com> ("Carlos =?utf-8?Q?S=C3=A1nchez?= de La Lama"'s message of "Mon, 24 Oct 2016 16:35:09 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Carlos =?utf-8?Q?S=C3=A1nchez?= de La Lama Cc: guix-devel@gnu.org csanchezdll@gmail.com (Carlos S=C3=A1nchez de La Lama) writes: >> On Mon, Oct 24, 2016 at 09:51:53AM +0200, Carlos S=C3=A1nchez de La Lama= wrote: >>> gcc-4.9.3 has a bug in long double isinf builtin on PowerPC, which >>> affects glibc versions >=3D 2.23. >>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D70117 >>>=20 >>> * gnu/packages/gcc.scm (gcc-4.9): Update to 4.9.4. >> >> Is this different from what we have on core-updates? >> >> http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/gcc.scm?h=3D= core-updates#n339 > > Not at all. I am not tracking core-updates, so I had missed that. I > will check there in the future. Sorry about that. > > BTW, is there described somewhere which kind of updates go to > core-updates first? Does everything go first to core-updates? Most changes go to 'master' first and are later merged into 'core-updates'. However, changes that would force a large number of rebuilds need to be pushed to another branch, to allow our build farm to rebuild before its merged to 'master'. 'gcc-4.9' is our default compiler, so it would force a rebuild of _everything_. Changes like that are precisely what 'core-updates' is for. > I am trying to understand to decide on whether I should use cote-updates > as a basis for my contributions instead of master. If you are porting to a new architecture, I would definitely recommend basing your work on 'core-updates', which will likely be merged into 'master' in the next two weeks. If you need gcc-4.9.4, that's another reason to base your work on 'core-updates'. Thanks for your efforts! Mark