Shailesh Tripathi
B.Tech. Part-IV
Electronics Engineering
IIT-BHU (Varanasi)
On Tue, Mar 21, 2017 at 2:51 AM, Vasco Alexandre da Silva Costa <
vasco.co...@gmail.com> wrote:
> On Mon, Mar 20, 2017 at 2:54 PM, Shailesh Tripathi <
> shailesh.tripathi.ec...@itbhu.ac.in> wrote:
>
>> Hello,
>> A few
On Mon, Mar 20, 2017 at 2:54 PM, Shailesh Tripathi <
shailesh.tripathi.ec...@itbhu.ac.in> wrote:
> Hello,
> A few more doubts!
>
> 1. For the NEAR_ZERO function in "common.cl", the epsilon value used
> should be *"RT_PCOEFF_TOL"* or *"RT_DOT_TOL"? *Basically, what are
> these two different
Hello,
A few more doubts!
1. For the NEAR_ZERO function in "common.cl", the epsilon value used should
be *"RT_PCOEFF_TOL"* or *"RT_DOT_TOL"? *Basically, what are these two
different tolerance value for?
2. In the "part", "rhc" and "rpc" codes, in place of "*segp->seg_in"*
and "*segp->seg_out",
Hey Vasco,
Thanks a lot :)
That was a lot of knowledge in a single go :)
I will try these out and I hope to complete the task correctly ASAP :)
Regards
Shailesh
Shailesh Tripathi
B.Tech. Part-IV
Electronics Engineering
IIT-BHU (Varanasi)
On Mon, Mar 20, 2017 at 2:59 PM, Vasco Alexandre da
Most of the vector macros are available as standard OpenCL operators or
functions. You can get a listing of those here:
https://www.khronos.org/files/opencl-1-2-quick-reference-card.pdf
e.g. VSCALE(a, b, c) can be replaced with a = b * c
So yes you can use translate the code like you mentioned.
On Sun, Mar 19, 2017 at 6:41 PM, Shailesh Tripathi , B.Tech., Electronics
Engg., IIT (BHU), Varanasi (INDIA)
wrote:
> Hello,
> While writing the.cl file, I got stuck at a data type "*bn_poly_t*" and "
> *bn_complex_t*". To use this in kernels, can these
Hello,
Sorry for flooding the list with so many questions :/ Last set for queries
for the day :)
1. How to use these functions '*rt_poly_roots', 'bu_log'*, *'bn_pr_roots' *and
'*VPRINT*' in the kernels (.cl file)
2. Why are functions like '*RT_GET_SEG' *eliminated in the the kenels and
how does