From: Jost Berthold <jb.diku@gmail.com>
To: types-announce@lists.seas.upenn.edu, caml-list@inria.fr,
hipeac-announce@hipeac.net, prog-lang@diku.dk
Subject: [Caml-list] Call for participation: Functional High-Performance Computing (FHPC) 2014
Date: Fri, 25 Jul 2014 20:01:33 +0200 [thread overview]
Message-ID: <53D29B7D.80102@gmail.com> (raw)
The 3rd ACM SIGPLAN Workshop on Functional High Performance Computing
(FHPC 2014) will be held in Gothenburg on September 4 (immediately after
ICFP).
FHPC features exciting talks about a range of topics: optimizing
compilation, GPU computing, computing on heterogeneous platforms, as
well as parallel applications and programming patterns.
It will be a very enjoyable workshop so please consider attending.
The full workshop programme is available at
https://sites.google.com/site/fhpcworkshops/fhpc-2014/programme
Registration for FHPC is done using the ICFP registration site.
Online registration for both ICFP and FHPC starts here:
https://regmaster4.com/2014/ICFP14/ic01code/regsystem.php?control=register
Note that the last day for early registration at ICFP and associated
workshops is August 3!
With best wishes
Mary Sheeran, Ryan Newton, and Jost Berthold
reply other threads:[~2014-07-25 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53D29B7D.80102@gmail.com \
--to=jb.diku@gmail.com \
--cc=caml-list@inria.fr \
--cc=hipeac-announce@hipeac.net \
--cc=prog-lang@diku.dk \
--cc=types-announce@lists.seas.upenn.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox