Type casting in OpenCL APIs (void *)&c_mem_obj
I have encountered a strange syntax inside armaments list of OpenCL host-code. However, I do not have any problem with my hostcode functionality but it is strange for me what does it mean at all and why it pass the arguments in this way.
clSetKernelArg(kernel, 0, sizeof(cl_mem), (void *)&c_mem_obj);
To the best of my knowledge, it is type cast. am i wrong ?
i believe it does not have any special purpose since the clSetKernelArg API already accept only pointer.
It is really helpful to have a more technical explanation.
thanks,
jimbo
opencl
add a comment |
I have encountered a strange syntax inside armaments list of OpenCL host-code. However, I do not have any problem with my hostcode functionality but it is strange for me what does it mean at all and why it pass the arguments in this way.
clSetKernelArg(kernel, 0, sizeof(cl_mem), (void *)&c_mem_obj);
To the best of my knowledge, it is type cast. am i wrong ?
i believe it does not have any special purpose since the clSetKernelArg API already accept only pointer.
It is really helpful to have a more technical explanation.
thanks,
jimbo
opencl
add a comment |
I have encountered a strange syntax inside armaments list of OpenCL host-code. However, I do not have any problem with my hostcode functionality but it is strange for me what does it mean at all and why it pass the arguments in this way.
clSetKernelArg(kernel, 0, sizeof(cl_mem), (void *)&c_mem_obj);
To the best of my knowledge, it is type cast. am i wrong ?
i believe it does not have any special purpose since the clSetKernelArg API already accept only pointer.
It is really helpful to have a more technical explanation.
thanks,
jimbo
opencl
I have encountered a strange syntax inside armaments list of OpenCL host-code. However, I do not have any problem with my hostcode functionality but it is strange for me what does it mean at all and why it pass the arguments in this way.
clSetKernelArg(kernel, 0, sizeof(cl_mem), (void *)&c_mem_obj);
To the best of my knowledge, it is type cast. am i wrong ?
i believe it does not have any special purpose since the clSetKernelArg API already accept only pointer.
It is really helpful to have a more technical explanation.
thanks,
jimbo
opencl
opencl
asked Nov 14 '18 at 20:30
Mehdi Roozmeh mehdjimboMehdi Roozmeh mehdjimbo
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You are right, it is a type cast. It is taking the address of your cl_mem
object (which is type cl_mem *
) and casting it to type void *
(and since clSetKernelArg takes a const void *
it's not even the best cast).
It is not required. You could also just write clSetKernelArg(kernel, 0, sizeof(cl_mem), &c_mem_obj)
and it should compile (it does for our code, on Windows, Mac, and Linux).
Thanks!!! Yes you are right. it works without cast. I did not understood why they used this kind of syntax and since it was from NVIDIA benchmark it become more interesting for me.
– Mehdi Roozmeh mehdjimbo
Nov 15 '18 at 13:19
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308290%2ftype-casting-in-opencl-apis-void-c-mem-obj%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You are right, it is a type cast. It is taking the address of your cl_mem
object (which is type cl_mem *
) and casting it to type void *
(and since clSetKernelArg takes a const void *
it's not even the best cast).
It is not required. You could also just write clSetKernelArg(kernel, 0, sizeof(cl_mem), &c_mem_obj)
and it should compile (it does for our code, on Windows, Mac, and Linux).
Thanks!!! Yes you are right. it works without cast. I did not understood why they used this kind of syntax and since it was from NVIDIA benchmark it become more interesting for me.
– Mehdi Roozmeh mehdjimbo
Nov 15 '18 at 13:19
add a comment |
You are right, it is a type cast. It is taking the address of your cl_mem
object (which is type cl_mem *
) and casting it to type void *
(and since clSetKernelArg takes a const void *
it's not even the best cast).
It is not required. You could also just write clSetKernelArg(kernel, 0, sizeof(cl_mem), &c_mem_obj)
and it should compile (it does for our code, on Windows, Mac, and Linux).
Thanks!!! Yes you are right. it works without cast. I did not understood why they used this kind of syntax and since it was from NVIDIA benchmark it become more interesting for me.
– Mehdi Roozmeh mehdjimbo
Nov 15 '18 at 13:19
add a comment |
You are right, it is a type cast. It is taking the address of your cl_mem
object (which is type cl_mem *
) and casting it to type void *
(and since clSetKernelArg takes a const void *
it's not even the best cast).
It is not required. You could also just write clSetKernelArg(kernel, 0, sizeof(cl_mem), &c_mem_obj)
and it should compile (it does for our code, on Windows, Mac, and Linux).
You are right, it is a type cast. It is taking the address of your cl_mem
object (which is type cl_mem *
) and casting it to type void *
(and since clSetKernelArg takes a const void *
it's not even the best cast).
It is not required. You could also just write clSetKernelArg(kernel, 0, sizeof(cl_mem), &c_mem_obj)
and it should compile (it does for our code, on Windows, Mac, and Linux).
answered Nov 15 '18 at 0:06
DithermasterDithermaster
5,5241817
5,5241817
Thanks!!! Yes you are right. it works without cast. I did not understood why they used this kind of syntax and since it was from NVIDIA benchmark it become more interesting for me.
– Mehdi Roozmeh mehdjimbo
Nov 15 '18 at 13:19
add a comment |
Thanks!!! Yes you are right. it works without cast. I did not understood why they used this kind of syntax and since it was from NVIDIA benchmark it become more interesting for me.
– Mehdi Roozmeh mehdjimbo
Nov 15 '18 at 13:19
Thanks!!! Yes you are right. it works without cast. I did not understood why they used this kind of syntax and since it was from NVIDIA benchmark it become more interesting for me.
– Mehdi Roozmeh mehdjimbo
Nov 15 '18 at 13:19
Thanks!!! Yes you are right. it works without cast. I did not understood why they used this kind of syntax and since it was from NVIDIA benchmark it become more interesting for me.
– Mehdi Roozmeh mehdjimbo
Nov 15 '18 at 13:19
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308290%2ftype-casting-in-opencl-apis-void-c-mem-obj%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown