On 14/02/2010 17:58, Don Stewart wrote:
igloo:
Hi all,
We are planning to remove the -fvia-c way of compiling code
(unregisterised compilers will continue to compile via C only, but
registerised compilers will only use the native code generator).
We'll probably deprecate -fvia-c in the 6.14
I've imported in my module: import Control.Concurrent.STM.
My question is: Have I to use -package stm in ghc command line options?
Thanks in advance.
Luca.
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
Hello Luca,
Monday, February 15, 2010, 8:01:11 PM, you wrote:
I've imported in my module: import Control.Concurrent.STM.
My question is: Have I to use -package stm in ghc command line options?
either use -package stm or --make. later automatically imports all
required packages
--
Best
Hi,
the things I am interested in are:
foldU f init .
mapU (\k - array_1 !: (i,k) `combine` array_2 !: (k,j)) $
enumFromToU i j
where (!:) = fancy_index_op
with both `vector` and `uvector` (then D.V.fold etc).
Since ghc 6.12 there has been no significant difference in using either
backend.
marlowsd:
Simon Marlow has recently fixed FP performance for modern x86 chips in
the native code generator in the HEAD. That was the last reason we know
of to prefer via-C to the native code generators. But before we start
the removal process, does anyone know of any other problems with the
Am Montag 15 Februar 2010 17:37:55 schrieb Simon Marlow:
On 14/02/2010 17:58, Don Stewart wrote:
igloo:
Hi all,
We are planning to remove the -fvia-c way of compiling code
(unregisterised compilers will continue to compile via C only, but
registerised compilers will only use the
dons:
marlowsd:
Simon Marlow has recently fixed FP performance for modern x86 chips in
the native code generator in the HEAD. That was the last reason we know
of to prefer via-C to the native code generators. But before we start
the removal process, does anyone know of any other
marlowsd:
On 03/02/2010 15:39, Simon Peyton-Jones wrote:
| Or we could switch to different quotation brackets altogether for
| quasiquotation, the obvious possibility being|...blah...|, and
| pads|...blah...|. That would not be hard, and would only affect the
| handful of current
