On Tue, Nov 3, 2015 at 8:43 AM, Clément Bœsch <u...@pkh.me> wrote: > On Tue, Nov 03, 2015 at 08:41:33AM -0500, Ganesh Ajjanagadde wrote: >> On Tue, Nov 3, 2015 at 8:36 AM, Clément Bœsch <u...@pkh.me> wrote: >> > On Tue, Nov 03, 2015 at 07:20:39AM -0500, Ganesh Ajjanagadde wrote: >> > [...] >> >> This is an opinion, so I will state mine here: if you are developing >> >> use ccache + GCC > ccache + clang > clang = gcc. Reason for the first >> >> is due to the terrible interaction ccache has with clang. >> > >> > I'm curious; what are you talking about here? >> >> Build is noisy: e.g glibc functions like strcmp when inline expanded >> cause -Warray-bounds all over the place whenever strcmp is used. There >> is a clang/glibc ticket for this, forget which. >> > > and the relationship with ccache interaction?
No idea, all I know is that it happens with ccache and not without. I don't know if it is a ccache bug, a clang bug, or both: but whatever it is, it happens iff both are present. Also see e.g discussion with Ronald on getting av_uninit to clang: we can't do it yet due to ccache bugs. That reminds me - I still need to file a ticket for it, but it is low priority for me due to my own favored usage of gcc. > > -- > Clément B. > > _______________________________________________ > 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