1. 24 Feb, 2012 1 commit
  2. 23 Feb, 2012 1 commit
  3. 17 Feb, 2012 1 commit
  4. 14 Feb, 2012 1 commit
  5. 31 Jan, 2012 2 commits
  6. 18 Jan, 2012 1 commit
  7. 17 Jan, 2012 1 commit
  8. 13 Jan, 2012 3 commits
  9. 12 Jan, 2012 3 commits
  10. 10 Jan, 2012 2 commits
  11. 06 Jan, 2012 2 commits
  12. 06 Dec, 2011 1 commit
    • dterei's avatar
      Fix trac # 5486 · fe60dd4a
      dterei authored
      LLVM has a problem when the user imports some FFI types
      like memcpy and memset in a manner that conflicts with
      the types that GHC uses internally.
      
      So now we pre-initialise the environment with the most
      general types for these functions.
      fe60dd4a
  13. 04 Dec, 2011 4 commits
  14. 29 Nov, 2011 1 commit
  15. 28 Nov, 2011 1 commit
    • Ian Lynagh's avatar
      Implement a capi calling convention; fixes #2979 · 36f8cabe
      Ian Lynagh authored
      In GHC, this provides an easy way to call a C function via a C wrapper.
      This is important when the function is really defined by CPP.
      
      Requires the new CApiFFI extension.
      
      Not documented yet, as it's still an experimental feature at this stage.
      36f8cabe
  16. 22 Nov, 2011 4 commits
  17. 17 Nov, 2011 1 commit
    • dterei's avatar
      Fix #4211: No need to fixup stack using mangler on OSX · 8a1c644a
      dterei authored
      We now manage the stack correctly on both x86 and i386, keeping
      the stack align at (16n bytes - word size) on function entry
      and at (16n bytes) on function calls. This gives us compatability
      with LLVM and GCC.
      8a1c644a
  18. 01 Nov, 2011 1 commit
    • dmp's avatar
      Change stack alignment to 16+8 bytes in STG code · a9ce3611
      dmp authored
      
      
      This patch changes the STG code so that %rsp to be aligned
      to a 16-byte boundary + 8. This is the alignment required by
      the x86_64 ABI on entry to a function. Previously we kept
      %rsp aligned to a 16-byte boundary, but this was causing
      problems for the LLVM backend (see #4211).
      
      We now don't need to invoke llvm stack mangler on
      x86_64 targets. Since the stack is now 16+8 byte algined in
      STG land on x86_64, we don't need to mangle the stack
      manipulations with the llvm mangler.
      
      This patch only modifies the alignement for x86_64 backends.
      Signed-off-by: dterei's avatarDavid Terei <davidterei@gmail.com>
      a9ce3611
  19. 15 Oct, 2011 1 commit
  20. 02 Oct, 2011 1 commit
  21. 25 Aug, 2011 2 commits
  22. 21 Aug, 2011 2 commits
    • kgardas's avatar
      enable ARM specific target data layout and triple again · 748883b4
      kgardas authored
      This patch is allowed by the 'on ARMv7 with VFPv3[D16] support pass
       appropriate -mattr value to LLVM llc' patch. The trick is that LLVM
      by default (probably!) does not enable VFP, but GHC requires it
      so LLVM's llc asserts on unavailable floating point register. i.e. GHC/LLVM
      backend compiles into LLVM code which is using floats, but llc thinks
      no float regs for this are available. Passing appropriate llc option
      which is implemented in patch mentioned above fixes this issue.
      748883b4
    • dterei's avatar
      Add popcnt support to LLVM backend · 2906db6c
      dterei authored
      2906db6c
  23. 10 Aug, 2011 3 commits