How to write Nested loop in Opencl

Question

1.00/5 (1 vote)

See more:

The original C code is

C#

void GaussianArray(float* Gauss, int variable){
    for(int i = 1; i < variable; i++ )
    {
        Gauss[i] = 1;
        for(int j = i - 1; j > 0; j-- )
        {
            Gauss[j] += Gauss[j - 1];
        }
    }
}

-----------------------------------------------------
I'm trying to make opencl kernel code.
how to change above function to kernel?

Posted 14-Aug-14 20:21pm

kyleK89

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-08-14T21:35:00

You misunderstand something very basic in computing. First, OpenCL is not a language, this is a framework: http://en.wikipedia.org/wiki/OpenCL[^].
So, first, the C language remains C language. Second: high-level languages languages produce the same code, for kernel or not, does not matter. In particular, the code of the body of the function works on stack, which is always available, as well as the stack pointer. The only problem is the first parameter, the pointer: it should point to the valid point in memory. But this is a matter of calling code, not the code you show, which is just fine.

—SA