problem is cudart and nvrtc aren't in the default path, i think only nvcc can find them easily. I might be able to hack around that simply by querying the path using nvcc
@athas: theres a problem with the #ifdef __cplusplus in the generated headers
they should not be around the other includes, only around the header's body
sorry i didn't contribute it myself btw
Last time i tried to build futhark it took a really long time and i'm not comfortable with making a pr without testing
it causes cuda.h to be interpreted as a c header when using from c++
they probably provide some extended functionality for c++
but then the header is interpreted as a c header and compilation fails
Orestis: i settled on the following, which now also supports cuda:
meson_options.txt:
option('futhark-backend', type: 'combo', choices: ['c', 'multicore', 'opencl', 'cuda'], value: 'c', description: 'Select the backend that Futhark code compiles to')meson.build:
dependencies = []
# Build futhark library
futhark = find_program('futhark')
futhark_backend = get_option('futhark-backend')
futhark_generated = custom_target(
'futhark',
input: 'src/main.fut',
output: ['futhark-generated.c', 'futhark-generated.h'],
command: [futhark, futhark_backend, '@INPUT@', '--library', '-o', 'futhark-generated']
)
if futhark_backend == 'multicore'
dependencies += dependency('threads')
elif futhark_backend == 'opencl'
dependencies += dependency('OpenCL')
elif futhark_backend == 'cuda'
dependencies += dependency('cuda', modules: ['cuda', 'cudart', 'nvrtc'])
endif
# Final executable
executable(
'my_exe',
[sources, futhark_generated],
dependencies: dependencies,
)
hello. how is the futhark test header parsed? is there a way to get the header and convert it into a text file?
There is a parser defined for it in Haskell code. I wouldn't mind adding commands for extracting that information in another format, if it would be useful.
I mean maybe just redirect to stdout or write it in a file so it's easy to pipe it into the tests executable manually
Usually a prettyprinted prefix of its contents.
-- Test simple indexing of an array.
-- ==
-- tags { firsttag secondtag }
-- input { [4,3,2,1] 1 }
-- output { 3 }
-- input { [4,3,2,1] 0 }
-- output { 0 }
let main (a: []i32) (i: i32): i32 =
a[i]
I mustbe doing something very stupid i guess:
futhark dataget test.fut #0
Junk argument: test.fut
Usage: futhark dataget program dataset
Options:
-V --version Print version information and exit.
-h --help Print help and exit.
thanks sorry
a last question if there are many tests all dataset have the same identifier. is there a way to distinguish them?
Well.. I guess if you have multiple datasets that are all just the same file. But then they would be identical anyway.
then both have #0 as id
Available datasets:
#0 ("[4i32, 3i32, 2i32, 1i32] 1i32")
#0 ("[4i32, 3i32, 2i32, 1i32] 2i32")
hello. I have a question. I played a bit with futhark autotune. it generated a .tuning file. how can I use the .tuning file within a program that is compiled from a futhark library?
That's sadly not fully automatic yet. You need to extract the sizes and then use the
futhark_context_config_set_size() function. The compiler itself uses this utility function: https://github.com/diku-dk/futhark/blob/master/rts/c/tuning.h
I've been meaning to make the tuning/library-integration smoother, but haven't gotten around to it yet (because we didn't have any libraries that benefited from tuning).
ok thanks. I got a speedup of like a factor 3-4 on futhark bench and was wondering how well it would perform on the "real" case.