| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next


Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

And Smugness; McCloskey Economics Trilogy; cmocka - Mocks for C; Concept Creep (Americans); Futhark - OpenCL Language; Moved / Gone; Fan and USB issues; Burgers in Santiago; The Origin of Icosahedral Symmetry in Viruses; autoenum on PyPI; Jars Explains; Tomato Chutney v3; REST; US Elections and Gender: 24 Point Swing; PPPoE on OpenSuse Leap 42.1; SuperMicro X10SDV-TLN4F/F with Opensuse Leap 42.1; Big Data AI Could Be Very Bad Indeed....; Cornering; Postcapitalism (Paul Mason); Black Science Fiction; Git is not a CDN; Mining of Massive Data Sets; Rachel Kaadzi Ghansah; How great republics meet their end; Raspberry, Strawberry and Banana Jam; Interesting Dead Areas of Math; Later Taste; For Sale; Death By Bean; It's Good!; Tomato Chutney v2; Time ATAC MX 2 Pedals - First Impressions; Online Chilean Crafts; Intellectual Variety; Taste + Texture; Time Invariance and Gauge Symmetry; Jodorowsky; Tomato Chutney; Analysis of Support for Trump; Indian SF; TP-Link TL-WR841N DNS TCP Bug; TP-Link TL-WR841N as Wireless Bridge; Sending Email On Time; Maybe run a command; Sterile Neutrinos; Strawberry and Banana Jam; The Best Of All Possible Worlds; Kenzaburo Oe: The Changeling; Peach Jam; Taste Test; Strawberry and Raspberry Jam; flac to mp3 on OpenSuse 42.1; Also, Sebald; Kenzaburo Oe Interview; Otake (Kitani Minoru) move Black 121; Is free speech in British universities under threat?; I am actually good at computers; Was This Mansplaining?; WebFaction / LetsEncrypt / General Disappointment; Sensible Philosophy of Science; George Ellis; Misplaced Intuition and Online Communities; More Reading About Japan; Visibilty / Public Comments / Domestic Violence; Ferias de Santiago; More (Clearly Deliberate); Deleted Obit Post; And then a 50 yo male posts this...; We Have Both Kinds Of Contributors; Free Springer Books; Books on Religion; Books on Linguistics; Palestinan Electronica; Books In Anthropology; Taylor Expansions of Spacetime; Info on Juniper; Efficient Stream Processing; The Moral Character of Crypto; Hearing Aid Info; Small Success With Go!; Re: Quick message - This link is broken; Adding Reverb To The Echo Chamber; Sox Audio Tools; Would This Have Been OK?; Honesty only important economically before institutions develop; Stegangraphy via PS4; OpenCL Mess; More Book Recommendations; Good Explanation of Difference Between Majority + Minority; Musical Chairs - Who's The Privileged White Guy; I can see straight men watching this conversation and laffing; Meta Thread Defending POC Causes POC To Close Account; Indigenous People Of Chile; Curry Recipe; Interesting Link On Marginality; A Nuclear Launch Ordered, 1962; More Book Recs (Better Person); It's Nuanced, And I Tried, So Back Off; Marx; The Negative Of Positive; Jenny Holzer Rocks

© 2006-2015 Andrew Cooke (site) / post authors (content).

Calling OpenCL from Octave / Matlab

From: andrew cooke <andrew@...>

Date: Wed, 9 Dec 2009 11:42:22 -0300

[I am optimising some Matlab code but, because I don't have a Matlab
licence on my local dev machine, am using Octave.  So what follows is
a bit odd, because I am using Octave, but via the Matlab-compatible
tools.  That doesn't affect the main points, though...]

Calling OpenCL from Octave / Matlab turns out to be (at least in a
simple case) very similar to calling C.  The main issues are (1) C/C++
interop and (2) libraries.

Currently the Octave code calls a C routine which, in turn, calls the
OpenCL C++ code.  The OpenCL C++ code is compiled into a library
(called "support" below).  I used this approach because I already knew
Octave (+ Matlab) can call C, and wasn't sure about C++.  So this
moves worries about C/C++ interop to the C level (where I know how to
deal with them) rather than the Octave/Matlab level (where live might
be more complicated).  In other words (to labour the point) I am using
C as the main interface to Octave / Matlab, not C++.

So the script to build the code looks like this:

g++ -fpic -Wall
-I/home/andrew/pkg/NVIDIA_GPU_Computing_SDK/shared/inc -o support.o -c
gcc -shared -Wl,-soname,libsupport.so -olibsupport.so support.o

gcc -o main main.c -L. -lsupport -L/usr/lib64/
-L/home/andrew/pkg/NVIDIA_GPU_Computing_SDK/shared/lib/linux -lOpenCL
-loclUtil -lshrutil -lstdc++

mkoctfile -v --mex singlec5.c -L. -lsupport -L/usr/lib64/
-L/home/andrew/pkg/NVIDIA_GPU_Computing_SDK/shared/lib/linux -lOpenCL
-loclUtil -lshrutil -lstdc++

(note the use of fpic - more on that below; also my toolkit is
installed in a non-standard location).  The "main" above is a separate
C program that calls the OpenCL routines.  Getting this working first
allowed me to fix basic errors without worrying about Octave.

The file singlec5.c is the "mex" file that handles the call from
Octave, unpacks/packs data structures and calls the OpenCl code in the
support library.

All the above is pretty normal, I think.  However, it won't work "out
of the box" because it requires that the support libraries (provided
by NVidia and used in their demos, which I based my code on) are
compiled only as ".a" (archive) libraries and not ".so" (shared
object) (this is on x86-64 Linux (OpenSuse 11.1)).

To build the libraries as shared objects, modify the following two
files so that "-fpic" is included in CXX and CC as well as LINK:


Then rebuild the libraries:

cd NVIDIA_GPU_Computing_SDK/OpenCL/common/obj/release
gcc -shared -Wl,-soname,liboclUtil.so -oliboclUtil.so oclUtils.cpp.o
mv liboclUtil.so ../../../common/lib/

cd NVIDIA_GPU_Computing_SDK/shared/obj/release
gcc -shared -Wl,-soname,libshrUtil.so -olibshrUtil.so shrUtils.cpp.o
mv libshrUtil.so ../../lib/

Finally, the LD_LIBRARY_PATH should include


(Paths will need to be changed as appropriate - I hope that's obvious....!)


Extern C

From: andrew cooke <andrew@...>

Date: Wed, 9 Dec 2009 11:53:38 -0300

I should also have added, although I guess it's obvious, that the
header file for support.cpp, support.h, includes

  extern "C"

before each function declaration.  This lets C code link to the C++
routines (it removes the C++ name mangling, and may do other things I
do not understand).


Or Simply Don't Use The Libs

From: andrew cooke <andrew@...>

Date: Wed, 16 Dec 2009 11:53:00 -0300

Hmmm.  On another machine, working with Matlab rather than Octave, and
with CentOS rather than OpenSuse, the above failed to fix things.

So I revised my code.  For now I have changed the logging to use
printf().  Apart from that, the only critical support code used was
oclLoadProgSource.  That just reads the source into memory.  Reading
files in C is tedious, but not impossible; here's a replacement:

    FILE *file;
    size_t blockAvailable = 512;
    size_t blockRead;
    char *kernelSource = NULL;
    size_t kernelLength = 0;
    size_t currentSize = 0;

    printf("Loading %s\n", kernelPath);
    file = fopen(kernelPath, "r");
    if (! file) {
        printf("Could not find kernel\n");
        err = 1;
        goto cleanup;

    blockRead = blockAvailable;
    while (blockRead == blockAvailable) {
        blockAvailable *= 2;
        currentSize += blockAvailable;
        kernelSource = (char *)realloc(kernelSource, currentSize);
        blockRead = fread(kernelSource + kernelLength, sizeof(char),
                          blockAvailable, file);
        kernelLength += blockRead;
    *(kernelSource + kernelLength + 1) = 0;

You could add more checks (eg for realloc and fread) to handle more
errors, but the above works for now (this is very much proof of
concept code).


More On OpenCL and Matlab Here

From: andrew cooke <andrew@...>

Date: Thu, 17 Dec 2009 19:47:47 -0300



OpenCL and MATLAB - Amazing BLog. Help Needed.

From: Anushri Pampari <p.anushri25@...>

Date: Mon, 7 Jul 2014 05:17:17 +0530

Hello Andrew Cooke,

I am an undergraduate student working at Rice university. I have come
across your blog, Mex and OpenCL and I felt it very useful. Thank you so


I am currently running across a problem since a week. I dont know what the
issue could be. Hope you could help me. Thank you in advance.

So here is brief description of the issue.

I am trying to use OpenCL and Mex code. The Mex part of the code reads a
matlab dat file and the opencl code further runs the code on Intel CPU as
of now, though future plan would be to run it on a GPU. The Intel PLatform
is being recognized on just a normal OPENCL code ( without mex). But on
using the OPenCL with Mex, OpenCl fails to recognize the the Intel Platform
( platforms found 0).. I was wondering if you could help me through this. I
would be really grateful to you.

Thank you. Looking forward for your reply.

Third year Undergraduate.

Comment on this post