From: Keir Fraser <keir.xen@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
John McDermott CIV <john.mcdermott@nrl.navy.mil>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Mini-os fbfront.c unused variable complaint
Date: Wed, 08 Feb 2012 07:19:03 +0000 [thread overview]
Message-ID: <CB57D267.2A9D3%keir.xen@gmail.com> (raw)
In-Reply-To: <1328710520.6133.36.camel@zakaz.uk.xensource.com>
On 08/02/2012 14:15, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
> On Mon, 2012-02-06 at 19:05 +0000, John McDermott CIV wrote:
>> Xen Developers,
>>
>> FWIW, in trying to compile mini-os on Xen 4.1.2, I get a variable set
>> but not used warning for variable 'message' in function init_kbdfront.
>> (Looks like another one just like it, in function init_fbfront, from
>> the same file.) My source won't compile with these warnings. I could
>> not find a patch for this in xen-4.1-testing.hg Xenbits.
>
> This new, enabled by default, compiler warning is very annoying, even
> though it happens to be correct. Which distro has done it? (or maybe
> it's just new enough gcc which is to blame).
We should be disablign this warning in Config.mk, where we add
-Wno-unused-but-set-variable to CFLAGS. Perhaps mini-os needs to do the
same, if it is creating its own CFLAGS? Note that we add it in Config.mk via
$(call cc-option-add ...) because older gcc versions do not have this
warning.
-- Keir
>> It looks like a conditional printk got left out after the label
>> 'abort_transaction'. I don't understand fbfront.c well enough to
>> suggest a patch. Its low priority for me, because I am going to stick
>> some plausible code in there for now.
>
> I think an unconditional printk including the %s and message is all
> which is required here. If you've got some plausible code you may as
> well post it.
>
> Thanks,
> Ian.
>
>>
>> Sincerely,
>>
>> John
>> ----
>> What is the formal meaning of the one-line program
>> #include "/dev/tty"
>>
>> J.P. McDermott building 12
>> Code 5542 john.mcdermott@nrl.navy.mil
>> Naval Research Laboratory voice: +1 202.404.8301
>> Washington, DC 20375, US fax: +1 202.404.7942
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-02-08 7:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 19:05 Mini-os fbfront.c unused variable complaint John McDermott CIV
2012-02-08 14:15 ` Ian Campbell
2012-02-08 7:19 ` Keir Fraser [this message]
2012-02-09 9:05 ` Ian Campbell
2012-02-09 16:08 ` Ian Jackson
2012-02-09 16:09 ` Ian Campbell
2012-02-09 17:00 ` John McDermott CIV
2012-02-09 17:20 ` Ian Jackson
2012-02-09 17:29 ` John McDermott CIV
2012-02-13 12:43 ` Ian Campbell
2012-02-13 14:53 ` John McDermott CIV
2012-02-13 15:06 ` Ian Campbell
2012-02-13 16:07 ` John McDermott CIV
2012-02-13 17:02 ` Ian Jackson
2012-02-20 18:56 ` Ian Jackson
2012-02-08 15:01 ` John McDermott CIV
2012-02-09 9:10 ` Ian Campbell
2012-02-09 15:28 ` John McDermott CIV
2012-02-09 15:41 ` Ian Campbell
2012-02-09 16:07 ` Ian Jackson
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=CB57D267.2A9D3%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=john.mcdermott@nrl.navy.mil \
--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).