Error using gpucoder.profile (line 41)

Justin Hontz 2022-11-3

This appears to be a limitation with gpucoder.profile in that it does not properly handle certain codegen input specification types created with e.g. coder.typeof. I will submit an enhancement request for this.

For your particular example, can you try manually converting the codegen inputs to the runtime inputs and then pass the runtime inputs to gpucoder.profile? For instance, coder.typeof(1) should be converted to 1.

Emiliano Rosso 2022-11-4

编辑：Emiliano Rosso 2022-11-4

在 MATLAB Online 中打开

I think I have not understood well the use of coder.typeof. Among other things, the manual says not to use it to compile mex files. Anyway I tried :

ARGS {1} {1} = coder.typeof (1, [sz1 sz2]);

&

ARGS {1} {1} = coder.typeof (1, [sz1 sz2], 'Gpu', true);

&

ARGS {1} {1} = coder.typeof (0, [sz1 sz2], 'Gpu', true);

I forgot 'Gpu', true !!!

The first gives me the same error:

Error using gpucoder.profile (line 41)
Incorrect class for expression 'a': expected 'double' but found 'coder.PrimitiveType'.

The 2° & 3° give me:

Error using gpucoder.profile (line 41)
The input must contain numeric or logical data. 

This is my original working code for codegen:

[mex1,mex2]=size(x);
ARGS = cell(1,1);
ARGS{1} = cell(5,1);
ARGS{1}{1} = coder.typeof(0,[mex1 mex1]);
ARGS{1}{2} = coder.typeof(0,[mex1 1]);
ARGS{1}{3} = coder.typeof(0,[mex1 1]);
ARGS{1}{4} = coder.typeof(0);
ARGS{1}{5} = coder.typeof(0,[mex1 1]);
cfg = coder.gpuConfig('mex');
cfg.GpuConfig.CompilerFlags = '--fmad=false';
cfg.GenerateReport = true;
cfg.GpuConfig.ComputeCapability='5.2';
cfg.MATLABSourceComments=true;
codegen -config cfg myH_MEX -args ARGS{1}

There's a problem with ARGS{1}{4} when using 'Gpu',true because it's scalar but I verified it on a different example.

And this is the proflier code which gives me the error:

cfg = coder.gpuConfig('exe');
cfg.GpuConfig.MallocMode = 'discrete';
gpucoder.profile('myH_MEX',ARGS{1},'CodegenConfig',cfg,...
    'CodegenArguments','-d profilingdir','Threshold',0.001);
Thanks!

Justin Hontz 2022-11-4

在 MATLAB Online 中打开

In your example, can you try changing

ARGS{1}{1} = coder.typeof(0,[mex1 mex1]);

to something like

ARGS{1}{1} = zeros(mex1, mex1);

and do something similar for the other inputs? If you want the input to be passed on GPU, you can instead do

ARGS{1}{1} = zeros(mex1, mex1, 'gpuArray');

but for SIL execution, I'm not sure there is much reason to want to use GPU inputs.

Emiliano Rosso 2022-11-5

SOLVED.

it works for both cases (with and without gpuarray).

Is this profiling equivalent to my code in codegen or are there differences?

Why was it returning an error?

What is the difference if I use "'Gpu', true" in coder.typeof?

THANKS!

Justin Hontz 2022-11-7

The code generated for profiling is roughly the same as the code generated from usual SIL codegen, though with some additional profiling API calls inserted in some places to enable the profiling to work as expected.

The error was occurring because the profiler was trying to pass the codegen input specification value (e.g. produced by coder.typeof) to the SIL executable, which is not valid as a runtime input.

The 'Gpu' option of coder.typeof simply controls whether the input of the generated entry-point function will be passed on GPU or not. This can improve performance by eliminating cudaMemcpy calls each time the entry-point function is executed in the case the input comes from GPU (e.g. a GPU array input for MEX).

Emiliano Rosso 2022-11-8

Thanks for all! I finished.

Error using gpucoder.profile (line 41)

6 个评论
显示 4更早的评论隐藏 4更早的评论

回答（0 个）

类别

产品

版本

标签

Community Treasure Hunt

Error using gpucoder.profile (line 41)

6 个评论 显示 4更早的评论 隐藏 4更早的评论

回答（0 个）

类别

产品

版本

标签

另请参阅

Community Treasure Hunt

6 个评论
显示 4更早的评论隐藏 4更早的评论