Futhark – A small programming language that compiles to efficient GPU code
1–10 of 16 posts
Re: Futhark – A small programming language that compiles to efficient GPU code
#2*
This is NOT APL.
Futhark is a functional language, we will start with the obligatory factorial program:
fun fact (n: i32): i32 = reduce () 1 (map (1+) (iota n))
This has nothing to do with APL.
Perhaps a more apt title would be "Python for the GPU".j
*
There is a paper on this subject, where an APL interpreter is written in FUTARK, but then most compilers are written in C. In reality the technology in question is Futark on GPU.
Re: Futhark – A small programming language that compiles to efficient GPU code
#3Re: Futhark – A small programming language that compiles to efficient GPU code
#4Looks very interesting :) but I can't quite find out what is going on on the GPU. What GPU operations are executed for a sample program which contains various (scalar, vector, applying to different sizes and shapes etc.) operators?
Re: Futhark – A small programming language that compiles to efficient GPU code
#5Also, please change the title on this thread to have it reflect the same.
Re: Futhark – A small programming language that compiles to efficient GPU code
#6This is not APL. Please don't call it APL. Also, please change the title on this thread to have it reflect the same.
"APL on GPUs - A TAIL from the Past, Scribbled in Futhark
A paper describing an APL compiler (apltail) that operates by translating APL into a typed array intermediate language (TAIL), and from there into Futhark. While the Futhark details are light, the paper demonstrates a simple use of Futhark as a target language for a compiler. We succeed in achieving decent speedup on several (small) APL programs."
The introduction of the paper says it only "compiles a subset of APL into TAIL" though.
Re: Futhark – A small programming language that compiles to efficient GPU code
#7Really what does this have to do with APL ( Ken Iverson )?? * This is NOT APL. Futhark is a functional language, we will start with the obligatory factorial program: fun fact (n: i32): i32 = reduce ( ) 1 (map (1+) (iota n)) This has nothing to do with APL. Perhaps a more apt title would be "Python for the GPU".j * There is a paper on this subject, where an APL interpreter is written in FUTARK, but then most compilers…
Why Python? Futhark is a purely functional language and looks a lot like Haskell, so I think "Haskell for the GPU" would be a better title
Re: Futhark – A small programming language that compiles to efficient GPU code
#8Really what does this have to do with APL ( Ken Iverson )?? * This is NOT APL. Futhark is a functional language, we will start with the obligatory factorial program: fun fact (n: i32): i32 = reduce ( ) 1 (map (1+) (iota n)) This has nothing to do with APL. Perhaps a more apt title would be "Python for the GPU".j * There is a paper on this subject, where an APL interpreter is written in FUTARK, but then most compilers…
Re: Futhark – A small programming language that compiles to efficient GPU code
#9Really what does this have to do with APL ( Ken Iverson )?? * This is NOT APL. Futhark is a functional language, we will start with the obligatory factorial program: fun fact (n: i32): i32 = reduce ( ) 1 (map (1+) (iota n)) This has nothing to do with APL. Perhaps a more apt title would be "Python for the GPU".j * There is a paper on this subject, where an APL interpreter is written in FUTARK, but then most compilers…
> Perhaps a more apt title would be "Python for the GPU" Why Python? Futhark is a purely functional language and looks a lot like Haskell, so I think "Haskell for the GPU" would be a better title
OCaml would be an even more apt comparison.
I find it a bit ironic that of all the related submissions I (and others) have made, it's the one with the bizarre title that hits the front page!
Re: Futhark – A small programming language that compiles to efficient GPU code
#10Earlier quoted context omitted.
> Perhaps a more apt title would be "Python for the GPU" Why Python? Futhark is a purely functional language and looks a lot like Haskell, so I think "Haskell for the GPU" would be a better title
(Author here.) OCaml would be an even more apt comparison. I find it a bit ironic that of all the related submissions I (and others) have made, it's the one with the bizarre title that hits the front page!