From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65968] Massive memory corruption in Planetary Annihilation Alpha
Date: Sat, 22 Jun 2013 12:34:28 +0000 [thread overview]
Message-ID: <bug-65968-502-RIqVo4elpv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-65968-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 953 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65968
--- Comment #6 from Andreas Ringlstetter <andreas.ringlstetter@gmail.com> ---
RADEON_DEBUG=noopt is not possible, the pixel shader programs are to big to be
loaded without size optimizations.
Hard limit of 512 instruction slots per pixel shader:
http://developer.amd.com/wordpress/media/2012/10/Radeon_X1x00_Programming_Guide.pdf
page 13
This limit is exceeded by far due to all the virtual texturing code, the
optimized shader barely fits.
I did try it in 9.0 and 9.1 with noopt and I did get past the segfault in
peephole_mul_omod() this way, but it did fail then because the resulting shader
program was to big.
Deactivating hyper-z has no measurable impact, and it didn't prevent the
corruption either.
Antialiasing hasn't even been enabled in the application by default, so turning
it off makes no difference at all.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1859 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-06-22 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 12:55 [Bug 65968] New: Massive memory corruption in Planetary Annihilation Alpha bugzilla-daemon
2013-06-20 12:56 ` [Bug 65968] " bugzilla-daemon
2013-06-20 12:56 ` bugzilla-daemon
2013-06-20 12:58 ` bugzilla-daemon
2013-06-20 13:10 ` bugzilla-daemon
2013-06-20 13:57 ` bugzilla-daemon
2013-06-22 11:47 ` bugzilla-daemon
2013-06-22 12:34 ` bugzilla-daemon [this message]
2017-02-10 3:04 ` bugzilla-daemon
2017-02-10 3:11 ` bugzilla-daemon
2017-02-10 3:51 ` bugzilla-daemon
2017-02-14 5:21 ` bugzilla-daemon
2017-02-14 12:03 ` bugzilla-daemon
2017-02-14 17:50 ` 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-65968-502-RIqVo4elpv@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 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).