On 18 March 2015 at 22:22, John Snow <js...@redhat.com> wrote: > I just found this particular instance of a ccache-provoked warning > interesting because it does have some validity to it and I wanted to raise > the issue. > > If nobody cares, then, well. Nobody cares.
Well, I do sort of care, but on the other hand there are a lot of issues with linux-user that are more immediately interesting, so the temptation is to handwave this away, especially since I don't see the warning on *my* configs :-) If you want to provide patches to fix them (it genuinely is a bug that we don't check the return values here) I'm happy to review them. I do seem to recall having fixed some issues where clang warned about this in the past, eg commit f296c0d17. -- PMM
