#3138: Returning a known constructor: GHC generates terrible code for cmonad
-+--
Reporter: simonpj |Owner:
Type: run-time performance bug | Status: new
#781: GHCi on x86_64, cannot link to static data in shared libs
-+--
Reporter: guest |Owner:
Type: bug | Status: new
Priority: high |
On 01/06/2009 23:39, Sven Panne wrote:
So my question is again: Why is -fPIC not the default for GHC on x86_64? If we
don't want the overhead, that's OK (any benchmark numbers?), but then GHC's
documentation should really contain a big, fat warning that GHCi's dynamic
linker gets cases like the
#3253: validate failure (GCC warning)
--+-
Reporter: isaacdupree|Owner: simonmar
Type: bug| Status: closed
Priority: high |Milestone: 6.12.1
#3265: Type operators can be defined without the TypeOperators extension flag
-+--
Reporter: nibro |Owner: simonpj
Type: bug | Status: closed
#3268: implement the Cabal ${pkgroot} spec extension
-+--
Reporter: duncan|Owner:
Type: feature request | Status: new
Priority: normal|
#3241: System.Win32.Registry - incorrect length calculation in regSetStringValue
--+-
Reporter: binarin|Owner: simonmar
Type: bug| Status: closed
Priority:
#2650: Child processes always unwantedly inherit Handles on Windows
--+-
Reporter: Deewiant |Owner: simonmar
Type: bug| Status: closed
Priority: high
#3186: findExeutable does not respect order of search path on Windows
+---
Reporter: duncan |Owner: simonmar
Type: bug | Status: closed
Priority: normal
#2793: CLDouble is nothing like a long double
-+--
Reporter: jedbrown |Owner: igloo
Type: bug | Status: new
Priority: high |
#3271: New methods for Data.Sequence
-+--
Reporter: LouisWasserman| Owner:
Type: proposal | Status: new
Priority: normal| Component:
#3271: New methods for Data.Sequence
---+
Reporter: LouisWasserman | Owner:
Type: proposal | Status: new
Priority: normal | Milestone:
#3272: GHC panics when contexts are put late in function types
-+--
Reporter: dmwit | Owner:
Type: bug | Status: new
Priority:
13 matches
Mail list logo