Date: Sun, 17 Aug 2014 13:45:09 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, svn-src-stable-9@freebsd.org Subject: Re: svn commit: r270099 - in stable: 10/contrib/gcc/config/i386 9/contrib/gcc/config/i386 Message-ID: <20140817134509.GA47327@FreeBSD.org> In-Reply-To: <8CA269F6-BCD2-4E78-947F-682214367F36@FreeBSD.org> References: <201408171308.s7HD8Fnh099147@svn.freebsd.org> <20140817131942.GA38672@FreeBSD.org> <8CA269F6-BCD2-4E78-947F-682214367F36@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 17, 2014 at 03:29:42PM +0200, Dimitry Andric wrote: > In principle it is applicable, but the same file also has other changes > in head which were not MFCd, so just MFCing this one commit does not > make much sense. For example, the earlier cast fixes were part of a > much larger commit by Pedro Giffuni, adding "experimental support for > amdfam10/barcelona CPUs": > > http://svnweb.freebsd.org/base?view=revision&revision=251212 I'm running my stable/8 with Pedro's patches applied, including r251212, no problems so far (although I don't have recent AMD CPUs to play with). > Does it still make sense to backport such experimental changes to an old > stable branch? Of course I could split off just the changes to > emmintrin.h, and leave the others out, but then we would have a partial > MFC. I'm not sure if that is the usual way of doing things... Understood. My goal here is to try to keep stable/8 as alive as possible, since I plan to keep using it beyond its official EOL. Hence, when I see fixes that potentially help ports to be buildable on it I'd usually ask if they can be MFCed (when it's easy enough to do). ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140817134509.GA47327>