[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH] tests/cpu-policy: fix format-overflow warning by null terminating strings
- To: Jan Beulich <JBeulich@xxxxxxxx>
- From: Rich Persaud <persaur@xxxxxxxxx>
- Date: Fri, 2 Aug 2019 15:49:02 -0400
- Cc: Wei Liu <wl@xxxxxxx>, Oleksandr Andrushchenko <andr2000@xxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roman Shaposhnik <roman@xxxxxxxxxx>, IanJackson <ian.jackson@xxxxxxxxxxxxx>, "christopher.w.clark@xxxxxxxxx" <christopher.w.clark@xxxxxxxxx>, Jeff.Kubascik@xxxxxxxxxxxxxxx, Dario Faggioli <dfaggioli@xxxxxxxx>, Lars Kurth <lars.kurth.xen@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Roger Pau Monne <roger.pau@xxxxxxxxxx>
- Delivery-date: Fri, 02 Aug 2019 19:49:16 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 31.07.2019 02:22, Dario Faggioli wrote:Jan's example above, seem to compile **without any warnings** for me as
well. If I add a main(), I can even get the code above to print the
content of the array.
And yet, building the tools without a patch like Christoper's one
(which was also what I was using locally, and raised to Andy), I get:
Sure - I'm aware that we're using a (potentially heavily) patched gcc.Hence my question to Christopher whether he's using a plain one.
The Xen test-cpu-policy.c build error and workaround reported by Christopher can be reproduced by building Xen staging against upstream OpenEmbedded/Yocto meta-virtualization master and GCC. I've tested on Devuan Ascii with "oe-build-xen x86-64 staging master":
If there is an upstream GCC compiler issue, Xen will not be the only affected project. We can expect new data as other projects start building with recent GCC versions. In the meantime, the workaround can unblock Xen builds.
Rich |
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
