From: Brad Smith <brad@comstyle.com>
To: Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/vvfat: Fix compiler warnings for OpenBSD
Date: Mon, 16 Dec 2013 22:12:27 -0500 [thread overview]
Message-ID: <52AFC11B.7000707@comstyle.com> (raw)
In-Reply-To: <1386794231-18119-1-git-send-email-sw@weilnetz.de>
On 11/12/13 3:37 PM, Stefan Weil wrote:
> The buildbot shows these compiler warnings:
>
> block/vvfat.c: In function 'create_short_and_long_name':
> block/vvfat.c:620: warning: array size (8) smaller than bound length (11)
> block/vvfat.c:620: warning: array size (8) smaller than bound length (11)
> block/vvfat.c:635: warning: array size (8) smaller than bound length (11)
> block/vvfat.c:635: warning: array size (8) smaller than bound length (11)
This is due to an OpenBSD specific GCC bounds checker.
- gcc recognizes a new flag, -Wbounded, to perform basic checks
on functions which accept buffers and sizes. An extra
attribute, __bounded__, has been added to mark functions that
can be checked this way.
There was another issue here..
CC hw/display/exynos4210_fimd.o
hw/display/exynos4210_fimd.c: In function 'exynos4210_fimd_reset':
hw/display/exynos4210_fimd.c:1342: warning: array size (16) smaller than
bound length (192)
hw/display/exynos4210_fimd.c:1342: warning: array size (16) smaller than
bound length (192)
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
prev parent reply other threads:[~2013-12-17 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 20:37 [Qemu-devel] [PATCH] block/vvfat: Fix compiler warnings for OpenBSD Stefan Weil
2013-12-12 8:22 ` Stefan Hajnoczi
2013-12-12 9:20 ` Kevin Wolf
2013-12-17 3:12 ` Brad Smith [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=52AFC11B.7000707@comstyle.com \
--to=brad@comstyle.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).