From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70199] clang+llvm from svn crashes when generating opencl code for 64 bit types
Date: Sun, 13 Oct 2013 12:41:50 +0000 [thread overview]
Message-ID: <bug-70199-502-xVQR552LnQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70199-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2582 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70199
--- Comment #8 from Peter Wu <lekensteyn@gmail.com> ---
Created attachment 87554
--> https://bugs.freedesktop.org/attachment.cgi?id=87554&action=edit
piglit test showing importance of parameter order
The order of parameters for long seems to matter. Output for the attached
piglit test (failing tests on top):
> Running kernel test: Arg0 = a + b
Using kernel add0
Setting kernel arguments...
Running the kernel...
Validating results...
Expecting 3 (0x3) with tolerance 0, but got 12884901888 (0x300000000)
Error at long[0]
Argument 0: FAIL
PIGLIT:subtest {'Arg0 = a + b' : 'fail'}
> Running kernel test: Arg1 = a + b
Using kernel add1
Setting kernel arguments...
Running the kernel...
Validating results...
Expecting 3 (0x3) with tolerance 0, but got 8589934593 (0x200000001)
Error at long[0]
Argument 1: FAIL
PIGLIT:subtest {'Arg1 = a + b' : 'fail'}
> Running kernel test: set arg0 to arg1
Using kernel set0
Setting kernel arguments...
Running the kernel...
Validating results...
Expecting 4 (0x4) with tolerance 0, but got 17179869184 (0x400000000)
Error at long[0]
Argument 0: FAIL
PIGLIT:subtest {'set arg0 to arg1' : 'fail'}
(Passing tests below:)
> Running kernel test: set arg1 to arg0
Using kernel set1
Setting kernel arguments...
Running the kernel...
Validating results...
Argument 1: PASS
PIGLIT:subtest {'set arg1 to arg0' : 'pass'}
> Running kernel test: Arg2 = a + b
Using kernel add2
Setting kernel arguments...
Running the kernel...
Validating results...
Argument 2: PASS
PIGLIT:subtest {'Arg2 = a + b' : 'pass'}
> Running kernel test: set arg0 to arg1 (indirected)
Using kernel setp0
Setting kernel arguments...
Running the kernel...
Validating results...
Argument 0: PASS
PIGLIT:subtest {'set arg0 to arg1 (indirected)' : 'pass'}
> Running kernel test: set arg1 to arg0 (indirected)
Using kernel setp1
Setting kernel arguments...
Running the kernel...
Validating results...
Argument 1: PASS
PIGLIT:subtest {'set arg1 to arg0 (indirected)' : 'pass'}
> Running kernel test: set arg0 to arg2 (with dummy pointer)
Using kernel set0_2
Setting kernel arguments...
Running the kernel...
Validating results...
Argument 0: PASS
PIGLIT:subtest {'set arg0 to arg2 (with dummy pointer)' : 'pass'}
> Running kernel test: set arg2 to arg0 (with dummy pointer)
Using kernel set2_0
Setting kernel arguments...
Running the kernel...
Validating results...
Argument 2: PASS
PIGLIT:subtest {'set arg2 to arg0 (with dummy pointer)' : 'pass'}
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3866 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-13 12:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 16:40 [Bug 70199] New: clang+llvm from svn crashes when generating opencl code for 64 bit types bugzilla-daemon
2013-10-06 16:40 ` [Bug 70199] " bugzilla-daemon
2013-10-06 16:41 ` bugzilla-daemon
2013-10-12 21:57 ` bugzilla-daemon
2013-10-12 22:03 ` bugzilla-daemon
2013-10-13 1:52 ` bugzilla-daemon
2013-10-13 3:29 ` bugzilla-daemon
2013-10-13 9:15 ` bugzilla-daemon
2013-10-13 12:41 ` bugzilla-daemon [this message]
2014-02-08 21:04 ` bugzilla-daemon
2015-12-21 12:53 ` bugzilla-daemon
2015-12-21 16:06 ` bugzilla-daemon
2017-03-22 15:35 ` bugzilla-daemon
2017-03-22 20:34 ` 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-70199-502-xVQR552LnQ@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).