From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96999] r600_shader.c:1590: warning: array subscript is above array bounds
Date: Tue, 19 Jul 2016 22:04:31 +0000 [thread overview]
Message-ID: <bug-96999-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1221 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96999
Bug ID: 96999
Summary: r600_shader.c:1590: warning: array subscript is above
array bounds
Product: Mesa
Version: git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: 0xe2.0x9a.0x9b@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Compiler: GCC 6.1.0
Mesa: git-0b626d7
$ grep "warning: array" media-libs:mesa-9999:20160719-211957.log
src/gallium/drivers/r600/r600_shader.c:1590:13: warning: array subscript is
above array bounds [-Warray-bounds]
src/gallium/drivers/r600/r600_shader.c:1591:13: warning: array subscript is
above array bounds [-Warray-bounds]
src/gallium/drivers/r600/r600_shader.c:1598:12: warning: array subscript is
above array bounds [-Warray-bounds]
src/gallium/drivers/r600/r600_shader.c:1599:12: warning: array subscript is
above array bounds [-Warray-bounds]
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2601 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-07-19 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 22:04 bugzilla-daemon [this message]
2017-02-20 16:50 ` [Bug 96999] r600_shader.c:1590: warning: array subscript is above array bounds bugzilla-daemon
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=bug-96999-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.