From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76223] [radeonsi] luxmark segfault
Date: Mon, 09 Jun 2014 18:18:36 +0000 [thread overview]
Message-ID: <bug-76223-502-mAMzhQ3qHu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76223-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1543 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #6 from Aaron Watry <awatry@gmail.com> ---
If you're building from luxrays source, can you also try disabling image
support and seeing if the error changes?
For a source build, go to scenes/luxball/luxball.cfg, and add:
accelerator.imagestorage.enable = 1
When I do that, I get some errors related to missing built-in functions that
libclc is probably failing to provide:
[LuxRays] [OpenCL device::AMD CEDARIntersect] QBVH compilation error:
ray_funcs.cl:43:14: error: use of undeclared identifier 'INFINITY'
ray->maxt = INFINITY;
^
qbvh_kernel.cl:119:17: warning: implicit declaration of function 'isnotequal'
is invalid in C99
int4 cond = isnotequal(divisor, (float4)0.f) & isgreaterequal(b0,
(float4)0.f) &
^
qbvh_kernel.cl:119:52: warning: implicit declaration of function
'isgreaterequal' is invalid in C99
int4 cond = isnotequal(divisor, (float4)0.f) & isgreaterequal(b0,
(float4)0.f) &
^
qbvh_kernel.cl:121:4: warning: implicit declaration of function 'isgreater' is
invalid in C99
isgreater(t, ray4->mint);
^
qbvh_kernel.cl:206:21: warning: implicit declaration of function 'signbit' is
invalid in C99
const int signs0 = signbit(ray4.dx.s0);
^
[SLG] OpenCL ERROR: clBuildProgram(CL_BUILD_PROGRAM_FAILURE)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2290 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:[~2014-06-09 18:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 5:23 [Bug 76223] New: [radeonsi] luxmark segfault bugzilla-daemon
2014-03-21 14:19 ` [Bug 76223] " bugzilla-daemon
2014-03-22 6:08 ` bugzilla-daemon
2014-03-23 5:00 ` bugzilla-daemon
2014-06-08 18:05 ` bugzilla-daemon
2014-06-09 18:16 ` bugzilla-daemon
2014-06-09 18:18 ` bugzilla-daemon [this message]
2014-06-11 23:39 ` bugzilla-daemon
2014-06-17 16:05 ` bugzilla-daemon
2014-06-18 21:18 ` bugzilla-daemon
2014-06-18 21:19 ` bugzilla-daemon
2014-06-18 21:21 ` bugzilla-daemon
2014-06-27 0:44 ` bugzilla-daemon
2014-07-02 21:33 ` bugzilla-daemon
2015-01-24 8:29 ` bugzilla-daemon
2015-01-24 10:57 ` bugzilla-daemon
2015-01-31 15:18 ` bugzilla-daemon
2015-02-01 20:33 ` bugzilla-daemon
2015-02-05 6:03 ` bugzilla-daemon
2015-02-05 14:35 ` bugzilla-daemon
2015-02-07 7:34 ` bugzilla-daemon
2015-02-09 3:46 ` bugzilla-daemon
2015-02-09 5:26 ` bugzilla-daemon
2015-02-09 6:14 ` bugzilla-daemon
2015-02-10 5:15 ` bugzilla-daemon
2015-02-10 6:28 ` bugzilla-daemon
2015-02-21 5:28 ` 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-76223-502-mAMzhQ3qHu@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).