On Fri, Aug 14, 2015 at 8:05 PM, Michael Niedermayer <mich...@niedermayer.cc> wrote: > On Fri, Aug 14, 2015 at 12:57:35PM -0400, Ganesh Ajjanagadde wrote: >> On Fri, Aug 14, 2015 at 5:14 AM, Michael Niedermayer >> <mich...@niedermayer.cc> wrote: >> > On Thu, Aug 13, 2015 at 08:57:12PM -0400, Ganesh Ajjanagadde wrote: >> >> On Thu, Jul 30, 2015 at 4:06 PM, Ganesh Ajjanagadde >> >> <gajjanaga...@gmail.com> wrote: >> >> > Signed-off-by: Ganesh Ajjanagadde <gajjanaga...@gmail.com> > [...] >> I think in future such hacks should have the version number of the >> tool in the comment, > > i agree, this is very easy to forget though
Oops, forgot to reply to this with my completed analysis: It was fixed in GCC 4.6 released in 2011: https://gcc.gnu.org/gcc-4.6 which is part of debian stable as well: https://packages.debian.org/wheezy/gcc-4.6 Most setups should be past this threshold, except some things like that Solaris box you use with GCC 4.3.2. Applying this patch should not be a problem, unless you want a comment with the results of this analysis and a FIXME tag. > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Into a blind darkness they enter who follow after the Ignorance, > they as if into a greater darkness enter who devote themselves > to the Knowledge alone. -- Isha Upanishad > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
