On Oct 12, 2011, at 5:26 AM, Simon Marlow wrote:
On 11/10/2011 18:45, David Peixotto wrote:
Ok, I have attached a set of patches to support building the GHC
runtime with llvm-gcc. The patches are based off of commit
29a97fded4010bd01aa0a17945c84258e285d421 which was last Friday's HEAD
with GHC, because of its use
of either A) Global register variables of any kind, or B) the __thread
storage modifier.
David Peixotto did some work on this not too long ago as the issue of
compiling with Clang was raised. His branches include changes which
make the 'gct' variable use
I think the warnings are not a big concern. I silence both of them by adding
-optl-Wl,-no_compact_unwind,-no_pie to my ghc options in /usr/bin/ghc.
In 10.7 they changed the default linking options to create a PIE (position
independent executable). To create a PIE you have to compile all code as
I've attached a small patch that seems to fix the build. The problem was that
the `dtraceSparkCounters` function was getting called even when we were not
compiling for the threaded rts. The patch just moves the call inside the #ifdef
for the threaded rts.
The call had been placed outside the
Does it make a difference if you use the threaded vs. non-threaded runtime? I'm
seeing the odd behavior on Mac, but only for the single-threaed runtime.
http://hackage.haskell.org/trac/ghc/ticket/5282#comment:8
On Jul 7, 2011, at 2:45 PM, Matthew Farkas-Dyck wrote:
Sorry, I ought to have
Perhaps the /Users/MyUser/.ghc folder is causing your problem?
On Apr 20, 2011, at 2:33 AM, Luca Ciciriello wrote:
Hi All.
I'm using GHC with MacOS X 10.6.7 (Xcode4). I've installed GHC 7.0.3 and the
HackageDB package hsgsom. Then, for my motivation, I've uninstalled GHC.
To remove GHC I've
The relevant GHC ticket is: http://hackage.haskell.org/trac/ghc/ticket/5011,
which it seems has already been fixed in HEAD.
You can also check this thread on Haskell-Cafe which contains a few workarounds
for this problem:
http://www.haskell.org/pipermail/haskell-cafe/2011-March/090051.html
I'm getting a warning from the linker when building programs using the 64-bit
version of the release candidate on Mac OS X 10.6.
$ cat Hello.hs
module Main where
main = putStrLn Hello, World
$ ~/ghc-7/bin/ghc -fforce-recomp Hello.hs
[1 of 1] Compiling Main ( Hello.hs, Hello.o )
On Jan 10, 2011, at 5:19 AM, Simon Marlow wrote:
We're intrested in opinions from both active and potential GHC
developers/contributors. Let us know what you think - would this make life
harder or easier for you? Would it make you less likely or more likely to
contribute?
+1 for moving
On Dec 8, 2010, at 2:45 AM, Simon Peyton-Jones wrote:
If anyone has a favourite how to understand git doc, do point me at it.
You may have already tried these, but I've found the [official git tutorial][1]
to be pretty decent. The [second part][2] contains some details on how git sees
the
I spent some time looking at the code generated for llvm and the optimizations
it can apply. There were quite a bit of details to examine and I wrote it up
as blog post here:
http://www.dmpots.com/blog/2010/11/05/optimizing-haskell-loops-with-llvm.html.
To summarize, I found that it is possible
Hi Roman,
On Nov 5, 2010, at 6:44 PM, Roman Leshchinskiy wrote:
On 05/11/2010, at 23:22, David Peixotto wrote:
I spent some time looking at the code generated for llvm and the
optimizations
it can apply. There were quite a bit of details to examine and I wrote it up
as blog post here
On Nov 5, 2010, at 7:55 PM, Roman Leshchinskiy wrote:
On 06/11/2010, at 00:28, David Peixotto wrote:
Yes, the LLVM code has Sp, Hp, Base all annotated as noalias. I believe that
Sp, Hp, and Base should never alias, but a (boxed) R1 should always alias
with either Sp or Hp. I had a hard
On Nov 5, 2010, at 8:56 PM, Brandon S Allbery KF8NH wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/5/10 19:22 , David Peixotto wrote:
Probably there are some wins to be had by choosing a good optimization
sequence for the code generated from GHC, rather than just using
Hi Larry,
GHC allows you to work with unboxed types. Int# is the type of unboxed ints. I#
is a normal data constructor. So we can see that GHC represents a (boxed) Int
as a normal algebraic data type
data Int = I# Int#
which says that an Int is a type with a single constructor (I#) that wraps
On Sep 9, 2010, at 6:37 AM, Simon Marlow wrote:
On 09/09/2010 10:39, Christian Maeder wrote:
Christian Maeder schrieb:
Hi,
we call from our haskell application the metis prover via
System.Process.readProcessWithExitCode metis filename
However, we are not able to get rid of this
16 matches
Mail list logo
