From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64600] r600g pyrit OpenCL issue on HD6850
Date: Sat, 12 Oct 2013 22:30:03 +0000 [thread overview]
Message-ID: <bug-64600-502-eH7B5FA8mX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64600-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1864 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64600
--- Comment #14 from Peter Wu <lekensteyn@gmail.com> ---
Created attachment 87536
--> https://bugs.freedesktop.org/attachment.cgi?id=87536&action=edit
piglit test kernel with pyrit
The patches did avoid the crash, but the results are still invalid.
For convenience, I have added some test vectors and glue to the pyrit kernel. I
don't know if such a complex testcase is acceptable for piglit, hence I am
posting it here. Let me know if such a case is suitable for piglit and if it
should be posted to the piglit list too.
The test passes with the POCL implementation but not with the R600 one.
Without the patches the output is:
## Test: Pyrit WPA2-PSK accelerator
(/src/piglit/tests/cl/program/program-tester.c) ##
# Running on:
# Platform: Default
# Device: AMD BARTS
# OpenCL version: 1.1
# OpenCL C version: 1.1
# Build options: -cl-std=CL1.1
Program has been built successfully
> Running kernel test:
Using kernel opencl_pmk_kernel
Setting kernel arguments...
Running the kernel...
cl-program-tester: /src/llvm/include/llvm/MC/MCRegisterInfo.h:65: unsigned int
llvm::MCRegisterClass::getRegister(unsigned int) const: Assertion `i <
getNumRegs() && "Register number out of range!"' failed.
Stack dump:
0. Running pass 'Function Pass Manager' on module 'radeon'.
1. Running pass 'R600 Handle indirect addressing' on function
'@opencl_pmk_kernel'
Aborted (core dumped)
With branch tsellar/r600-private-mem-fixes, up to commit cf5d9a2:
[..]
Running the kernel...
Validating results...
Expecting 3201012614 (0xbecb9386) with tolerance 0, but got 844928435
(0x325c95b3)
Error at uint[0]
Argument 1: FAIL
PIGLIT:subtest {'' : 'fail'}
>> Some or all of the tests FAILED
# Result:
PIGLIT: {'result': 'fail' }
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2844 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-10-12 22:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 19:35 [Bug 64600] New: r600g pyrit OpenCL issue on HD6850 bugzilla-daemon
2013-05-14 23:18 ` [Bug 64600] " bugzilla-daemon
2013-09-15 15:15 ` bugzilla-daemon
2013-09-15 21:50 ` bugzilla-daemon
2013-09-17 17:53 ` bugzilla-daemon
2013-09-17 19:03 ` bugzilla-daemon
2013-09-17 19:21 ` bugzilla-daemon
2013-09-17 19:31 ` bugzilla-daemon
2013-09-17 19:42 ` bugzilla-daemon
2013-09-17 20:03 ` bugzilla-daemon
2013-09-19 1:14 ` bugzilla-daemon
2013-09-19 20:42 ` bugzilla-daemon
2013-10-10 17:58 ` bugzilla-daemon
2013-10-10 18:34 ` bugzilla-daemon
2013-10-12 22:30 ` bugzilla-daemon [this message]
2013-10-14 15:40 ` bugzilla-daemon
2013-10-14 16:16 ` bugzilla-daemon
2013-10-15 6:42 ` bugzilla-daemon
2013-10-15 22:56 ` bugzilla-daemon
2013-10-16 0:01 ` bugzilla-daemon
2013-10-16 19:58 ` bugzilla-daemon
2013-10-31 15:42 ` 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-64600-502-eH7B5FA8mX@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).