On Wed, Oct 12, 2016 at 12:00:56PM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: [Xen-devel] [PATCH for-4.8] ipxe: update to newer
> > That was eventually done. I'm not sure exactly when the change was
> > made. Does gcc -Wno-foo work properly on all the gcc's we care about ?
> Jan Beulich writes ("Re: [Xen-devel] [PATCH for-4.8] ipxe: update to newer
> > Just fyi I have run into an issue with -Wno-override-init use in Linux
> > 4.8 on gcc 4.1.x, so what you say doesn't appear to hold for all gcc
> > versions we permit to be used.
> Well, that answers my question above.
> I think the right approach is to:
> * Test -Wno-this-is-not-a-warning-option. If gcc accepts it,
> add -Wno-something to disable the nonnull check·
> * Review the misleading indentations and if there are only a few, fix
> them in a downstream patch. Or, if there are many, decide to
> tolerate them.
FAOD, I consider this sub-thread for "what should we do for stable
versions of Xen". This is orthogonal to whether we should upgrade our
in-tree ipxe version. In other words, I plan to commence with the
upgrade if there is no major issue is found next week.
Xen-devel mailing list