Dear GHC experts,
I have questions about the profiling usage in ghc-6.2.2.
I have set {-# SCC .. #-} at several points in my large program.
The report in a.out.prof is
(I have re-formatted it, for the lines were too long)
-
The pro-filing has proved its power once more.
My complex program has a fragment which generates many arithmetical
expressions, filtering out `reducible' ones and nub-bing them with
respect to the commutativity of some operators.
I expected the `reducible' test to take most of the cost.
But the
I was just trying to compile a package using ghc-6.3.3 and came up against a
problem with the '--version'flag. Specifically, I don't think that 'ghc-6.3.3
--version' doesn't report the version to stdout.
# ghc-6.3.3 --version conftest
# cat conftest
[conftest is empty]
#ghc-6.2 --version
# ghc-6.3.3 --version conftest
# cat conftest
[conftest is empty]
Just updated my source and this works now.
This was a dup of Krasimir's problem anyway.
- Alson
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
I would prefer to keep them on the list. There are already a number of
different lists, and (of course IMO) I can't see a need to read _only_
feature requests, so why separate them?
Adding a tag to the email that would let maildrop or procmail deliver
it to a different folder would be a nice
I recently did a port of linux to ARM, and the floating point issue came up.
What happens is that if you don't do anything other than the default gcc
build, then every floating point call is converted to an O/S trap which
then does the floating point computation with the fixed point hardware
