From: Jens Axboe <axboe@kernel.dk>
To: Bruce Cran <bruce@cran.org.uk>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: gcc 5.1.1 and warnings when building fio on Linux with -flto
Date: Fri, 03 Jul 2015 14:27:30 -0600 [thread overview]
Message-ID: <5596F032.9070002@kernel.dk> (raw)
In-Reply-To: <5595B800.3030303@cran.org.uk>
On 07/02/2015 04:15 PM, Bruce Cran wrote:
> Noticed the following warnings when building fio on Linux with gcc 5.1.1
> and -flto:
>
> debug.h:38:22: warning: type of ‘fio_debug’ does not match original
> declaration
> extern unsigned long fio_debug;
> ^
> t/debug.c:5:14: note: previously declared here
> unsigned int fio_debug = 0;
Fixed that one up.
> lib/libmtd.c: In function ‘mtd_get_dev_info1’:
> lib/libmtd.c:751:46: warning: passing argument 3 of ‘dev_read_data’
> discards ‘const’ qualifier from pointer target type
> [-Wdiscarded-array-qualifiers]
> ret = dev_read_data(lib->mtd_name, mtd_num, &mtd->name,
> ^
> lib/libmtd.c:184:12: note: expected ‘void *’ but argument is of type
> ‘const char (*)[128]’
> static int dev_read_data(const char *patt, int mtd_num, void *buf, int
> buf_len)
> ^
> lib/libmtd.c:757:46: warning: passing argument 3 of ‘dev_read_data’
> discards ‘const’ qualifier from pointer target type
> [-Wdiscarded-array-qualifiers]
> ret = dev_read_data(lib->mtd_type, mtd_num, &mtd->type_str,
> ^
> lib/libmtd.c:184:12: note: expected ‘void *’ but argument is of type
> ‘const char (*)[65]’
> static int dev_read_data(const char *patt, int mtd_num, void *buf, int
> buf_len)
This one I know about, mtd is in need of some const cleaning. It is
currently reading into const strings.
--
Jens Axboe
prev parent reply other threads:[~2015-07-03 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 22:15 gcc 5.1.1 and warnings when building fio on Linux with -flto Bruce Cran
2015-07-03 20:27 ` Jens Axboe [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=5596F032.9070002@kernel.dk \
--to=axboe@kernel.dk \
--cc=bruce@cran.org.uk \
--cc=fio@vger.kernel.org \
/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