On 4/13/2018 10:48 AM, Michael Niedermayer wrote: > On Fri, Apr 13, 2018 at 10:33:32AM -0300, James Almer wrote: >> On 4/13/2018 9:59 AM, Michael Niedermayer wrote: >>> On Thu, Apr 12, 2018 at 10:17:51PM -0300, James Almer wrote: >>>> On 4/12/2018 9:11 PM, Michael Niedermayer wrote: >>> [...] >>> >>>>> >>>>> >>>>>> and apply the fix to the c11 check in configure. >>>>> >>>>> you want me to apply it ? >>>>> or i misunderstand ? >>>> >>>> You confirmed it worked ("foo += bar" and "bar = 0" alike), so push >>>> whichever you prefer, yes. >>> >>> do you have a link to your patch ? >> >> I gave you https://pastebin.com/qt6wBHG8 on IRC the other day to test, >> and you also tried a version using foo += bar instead of bar = 0. You >> mentioned both seemed to work, so as i said just push whichever you >> think is better, or just tell me which one to push if you're busy. > > iam always busy ;) > push what you prefer, push yours if you still cant decide > > thanks!
Pushed yours. I don't think we need to backport this to release/3.4 seeing the file using stdatomic.h you reported was failing (h264_slice.c) was ported to it only a month or so ago, but guess we'll know once the relevant fate client runs. I can see release/3.3 at least works. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel