0.16.2

Added

• futhark autotune: added --pass-option.

Fixed

• futhark bench: progress bar now correct when number of runs is
  less than 10 (#1050).

• Aliases of arguments passed for consuming parameters are now
  properly checked (#1053).

• When using a GPU backend, errors are now properly cleared.
  Previously, once e.g. an out-of-bounds error had occurred, all
  future operations would fail with the same error.

• Size-coercing a transposed array no longer leads to invalid code
  generation (#1054).

0.16.1

Added

• Incremental flattening is now performed by default. Use
  attributes to constrain and direct the flattening if you have
  exotic needs. This will likely need further iteration and
  refinement.

• Better code generation for reverse (and the equivalent explicit
  slice).

• futhark bench now prints progress bars.

• The cuda backend now supports similar profiling as the opencl
  option, although it is likely slightly less accurate in the
  presence of concurrent operations.

• A preprocessor macro FUTHARK_BACKEND_foo is now defined in
  generated header files, where foo is the name of the backend
  used.

• Non-inlined functions (via #[noinline]) are now supported in GPU
  code, but only for functions that exclusively operate on
  scalars.

• futhark repl now accepts a command line argument to load a
  program initially.

• Attributes are now also permitted on declarations and specs.

• futhark repl now has a :nanbreak command (#839).

Removed

• The C# backend has been removed (#984).

• The unsafe keyword has been removed. Use #[unsafe] instead.

Changed

• Out-of-bounds literals are now an error rather than a warning.

• Type ascriptions on entry points now always result in opaque types
  when the underlying concrete type is a tuple (#1048).

Fixed

• Fix bug in slice simplification (#992).

• Fixed a typer checker bug for tracking the aliases of closures
  (#995).

• Fixed handling of dumb terminals in futhark test (#1000).

• Fixed exotic monomorphisation case involving lifted type
  parameters instantiated with functions that take named parameters
  (#1026).

• Further tightening of the causality restriction (#1042).

• Fixed alias tracking for right-operand operator sections (#1043).

0.15.8

Added

• Warnings for overflowing literals, such as 1000 : u8.

• Futhark now supports an attribute system, whereby expressions can
  be tagged with attributes that provide hints or directions to the
  compiler. This is an expert-level feature, but it is sometimes
  useful.

0.15.7

Added

• Faster index calculations for very tight GPU kernels (such as the
  ones corresponding to 2D tiling).

• scan with vectorised operators (e.g. map2 (+)) is now faster
  in some cases.

• The C API has now been documented and stabilized, including
  obtaining profiling information (although this is still
  unstructured).

Fixed

• Fixed some cases of missing fusion (#953).

• Context deinitialisation is now more complete, and should not leak
  memory (or at least not nearly as much, if any). This makes it
  viable to repeatedly create and free Futhark contexts in the same
  process (although this can still be quite slow).

0.15.6

Added

• Binary operators now act as left-to-right sequence points with
  respect to size types.

• futhark bench now has more colourful and hopefully readable
  output.

• The compiler is now about 30% faster for most nontrivial programs.
  This is due to parallelising the inlining stage, and tweaking the
  default configuration of the Haskell RTS.

• futhark dataset is now about 8-10x faster.

Fixed

• Fixed some errors regarding constants (#941).

• Fixed a few missing type checker cases for sum types (#938).

• Fix OOB write in CUDA backend runtime code (#950).

0.15.5

Added

• reduce_by_index with f32-addition is now approximately 2x
  faster in the CUDA backend.

Fixed

• Fixed kernel extractor bug in if-interchange (#921).

• Fixed some cases of malformed kernel code generation (#922).

• Fixed rare memory corruption bug involving branches returning
  arrays (#923).

• Fixed spurious warning about entry points involving opaque return
  types, where the type annotations are put on a higher-order return
  type.

• Fixed incorrect size type checking for sum types in negative
  position with unknown constructors (#927).

• Fixed loop interchange for permuted sequential loops with more
  than one outer parallel loop (#928).

• Fixed a type checking bug for branches returning incomplete sum
  types (#931).

0.15.4

Added

• futhark pkg now shells out to curl for HTTP requests.

• futhark doc now supports proper GitHub-flavored Markdown, as it
  uses the cmark-gfm library internally.

• Top-level constants are now executed only once per program
  instance. This matters when Futhark is used to generate library
  code.

• futhark autotune is better at handling degrees of parallelism
  that assume multiple magnitudes during a single run.

• futhark pkg now uses curl to retrieve packages.

• Type errors are now printed in red for better legibility (thanks
  to @mxxo!).

Fixed

• Fixed incorrect handling of opaques in entry point return types.

• futhark pkg now works properly with GitLab (#899).

0.15.3

Added

• scan now supports operators whose operands are arrays. They are
  significantly slower than primitive-typed scans, so avoid them if
  at all possible.

• Precomputed constants are now handled much more efficiently.

• Certain large programs that rely heavily on inlining now compile
  orders of magnitude faster.

Fixed

• Some fixes to complicated module expressions.

• futhark pkg should no longer crash uncontrollably on network
  errors (#894).

• Fixed local open in interpreter (#887).

• Fix error regarding entry points that called other entry points
  which contained local functions (#895).

• Fix loading OpenCL kernels from a binary.

0.15.2

Fixed

• Fix a REPL regression that made it unable to handle overloaded
  types (such as numeric literals, oops).

• The uniqueness of a record is now the minimum of the uniqueness of
  any of its elements (#870).

• Bug in causality checking has been fixed (#872).

• Invariant memory allocations in scan/reduce operators are now supported.

• futhark run now performs more type checking on entry point input (#876).

• Compiled Futhark programs now check for EOF after the last input
  argument has been read (#877).

• Fixed a bug in loop type checking that prevented the result from
  ever aliasing the initial parameter values (#879).

0.15.1

Added

• Futhark now type-checks size annotations using a size-dependent
  type system.

• The parallel code generators can now handle bounds checking and
  other safety checks.

• Integer division by zero is now properly safety-checked and
  produces an error message.

• Integer exponentiation with negative exponent is now properly
  safety-checked and produces an error message.

• Serious effort has been put into improving type errors.

• reduce_by_index may be somewhat faster for complex operators on
  histograms that barely fit in local memory.

• Improved handling of in-place updates of multidimensional arrays
  nested in map. These are now properly parallelised.

• Added concat_to and flatten_to functions to prelude.

• Added indices function to the prelude.

• futhark check and all compilers now take a -w option for
  disabling warnings.

• futhark bench now accepts --pass-compiler-option.

• The integer modules now have mad_hi and mul_hi functions for
  getting the upper part of multiplications. Thanks to @porcuquine for the contribution!

• The f32 and f64 modules now also define sinh, cosh,
  tanh, asinh, acosh, and atanh functions.

• The f32 and f64 modules now also define fma and mad
  functions.

Removed

• Removed update, split2, intersperse, intercalate, pick,
  steps, and range from the prelude.

Changed

• "futlib" is now called "prelude", and it is now an error to
  import it explicitly.

Fixed

• Corrected address calculations in csharp backend.

• The C backends are now more careful about generating overflowing
  integer operations (since this is undefined behaviour in C, but
  defined in Futhark).

• futhark dataset no longer crashes uncontrollably when used
  incorrectly (#849).