From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Anthony Boorsma <Anthony.Boorsma@dornerworks.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/1] Compiler Warning Fix
Date: Wed, 07 Apr 2010 08:11:30 +0100 [thread overview]
Message-ID: <C7E1EEB2.FB35%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <D3E384327F5C6D48AADCEA84160B7D73012C9369@mcbain.dw.local>
This was fixed already 7-8 months ago. Seems your development tree is a tad
out of date.
-- Keir
On 06/04/2010 19:22, "Anthony Boorsma" <Anthony.Boorsma@dornerworks.com>
wrote:
> This patch fixes a compiler warning in the file xc_core.c. This fix is needed
> because warnings are treated as errors with the new gcc in Ubuntu 9.10.
>
> The fix was also included in a previous submission ³[Xen-devel] [PATCH 1/1]
> Xen ARINC653 scheduler² and is now being resubmitted as a separate patch.
>
> Anthony Boorsma
> www.DornerWorks.com <http://www.DornerWorks.com>
>
> diff -rupN a/SW/Xen/src/tools/libxc/xc_core.c
> b/SW/Xen/src/tools/libxc/xc_core.c
> --- a/SW/Xen/src/tools/libxc/xc_core.c 2010-04-06 12:59:44.343043800 -0400
> +++ b/SW/Xen/src/tools/libxc/xc_core.c 2010-04-06
> 13:01:36.359332600 -0400
> @@ -321,7 +321,15 @@ elfnote_dump_none(void *args, dumpcore_r
> struct xen_dumpcore_elfnote_none_desc none;
>
> elfnote_init(&elfnote);
> - memset(&none, 0, sizeof(none));
> + /*
> + * josh holtrop <DornerWorks.com> - 2009-01-04 - avoid compilation
> problem
> + * with warning "memset used with constant zero length parameter"
> and
> + * warnings treated as errors with the new gcc in Ubuntu 9.10
> + */
> + if (sizeof(none) > 0)
> + {
> + memset(&none, 0, sizeof(none));
> + }
>
> elfnote.descsz = sizeof(none);
> elfnote.type = XEN_ELFNOTE_DUMPCORE_NONE;
>
>
prev parent reply other threads:[~2010-04-07 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 18:22 [PATCH 1/1] Compiler Warning Fix Anthony Boorsma
2010-04-07 7:11 ` Keir Fraser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C7E1EEB2.FB35%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Anthony.Boorsma@dornerworks.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).