optionally dump effectively used tile, grid and block sizes
commit9479c2b5aa02a6e5f5093ac4df4261945dcbafdd
authorSven Verdoolaege <skimo@kotnet.org>
Wed, 28 May 2014 08:33:31 +0000 (28 10:33 +0200)
committerSven Verdoolaege <skimo@kotnet.org>
Wed, 28 May 2014 08:43:21 +0000 (28 10:43 +0200)
tree345a9b2acd3e0ef62688d122a5f7ac7c645c853f
parentf236328fbe5be5cfd33aa57e52c8611276c7d3db
optionally dump effectively used tile, grid and block sizes

As explained in the README, it can be difficult to predict how
the statements will be distributed over the kernels, but also
what the dimension of the tilable band will be that is tiled
and mapped to blocks and threads.  The README recommends the user
to first run PPCG with the defaults and to then examine the kernels.
This can be difficult to automate, however.
A dump of the effectively used tile, grrid and block sizes
is easier to analyze.

Requested-by: "Betts, Adam" <a.betts@imperial.ac.uk>
Tested-by: "Betts, Adam" <a.betts@imperial.ac.uk>
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
README
gpu.c
ppcg_options.c
ppcg_options.h