On Fri, 18 Jan 2019 at 17:41, Alex Bennée <alex.ben...@linaro.org> wrote: > > > Emilio G. Cota <c...@braap.org> writes: > > > On Thu, Jan 17, 2019 at 18:55:33 +0000, Peter Maydell wrote: > >> configure has logic to check whether it can use particular > >> warning enable/disable flags. Newer gcc (and I hope clang > >> but forget) will happily silently allow -Wno-random-new-thing > >> even if they don't support -Wrandom-new-thing) but I'm not > >> sure our minimum compiler version is yet new enough to > >> be able to rely on that (indeed the warning messages suggest > >> it is not). > > > > I figured that -Wno-unitialized is documented to work on both > > gcc and clang, and the change in testfloat drops the need > > for no-discarded-qualifiers, so we can go with this without > > messing with configure. > > Works for me, OK with you Peter?
If it builds on all the build machines it's ok. If it doesn't I'll bounce the pullreq and you can figure out a different approach :-) thanks -- PMM
