Hi,
Am Mittwoch, den 10.07.2013, 14:42 -0500 schrieb Nicolas Frisby:
2) Are the major GHC distributors planning on distributing
dynamically-linked ghc by default? GHC HQ, Haskell Platform,
http://www.haskell.org/ghc/distribution_packages?
You are talking about the GHC binary itself, not
Hi,
Am Montag, den 08.07.2013, 09:39 + schrieb Simon Peyton-Jones:
| If you CAN do that, then it's ok (internally) to use ordinary coercion
| lifting, roughly
|ntT g = T g refl
| The above per-constructor-arg testing is just to make sure that all
| the relevant witnesses are in
Hi,
despite my issues with recursive data types, I continued with the
implementation.
I now added the check if the data type arguments can safely be coerced.
I do not scan what is in scope for NT values to use, but rather expect
the progammer to promise the required witness when he uses deriving
On Sat, Jul 6, 2013 at 2:55 PM, Ian Lynagh i...@well-typed.com wrote:
On Fri, Jul 05, 2013 at 12:14:06PM -0500, Nicolas Frisby wrote:
I've been trying to let a statically-linked compiler shares its
FastString
table with plugins.
Why not use a dynamically linked compiler?
My main
Theoretically, ARM supports stage2 with the home-grown linker and a
statically linked GHC, but last I understood, it can't build
dynamically. That's because building the compiler with LLVM
dynamically is unsupported, and ARM can only use the LLVM backend.
There may be hope though; in commit
1. Was a quick hack that I did sometime in the past, it probably didn't
work fully. Nowadays LLVM does loopification, so its not clear whether
there's any benefit to doing it in cmm (but maybe there's some other payoff
that we can get by doing it earlier).
2. Is Edward Yang's optimisation pass.
Thank you both for explanations. I will try to clean up the code of Cmm
pipeline a little bit.
Janek
- Oryginalna wiadomość -
Od: Simon Marlow marlo...@gmail.com
Do: Jan Stolarek jan.stola...@p.lodz.pl
DW: ghc-devs@haskell.org
Wysłane: czwartek, 11 lipiec 2013 17:52:49
Temat: Re: Some
