[GHC] #11293: Compiler plugins don't work with profiling
GHC
ghc-devs at haskell.org
Tue Nov 29 05:01:44 UTC 2016
#11293: Compiler plugins don't work with profiling
-------------------------------------+-------------------------------------
Reporter: ezyang | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Profiling | Version: 7.11
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
| Unknown/Multiple
Type of failure: None/Unknown | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Rev(s):
Wiki Page: |
-------------------------------------+-------------------------------------
Changes (by angerman):
* cc: angerman (added)
Comment:
It's interesting to note that this is not only restricted to profiling and
non-profiling but crucial for cross compilation. It becomes more and more
obvious to me that profiling and cross compilation seem to share a fair
bit of preferred infrastructure.
In the cross compilation setting the plugin database would have to hold
packages compatible with the host, while the regular target database would
hold packages for the target platform.
Therefore I'm not certain this is or should be restricted to profiling
/non-profiling only. I'm also uncertain if it would make sense at some
point to have more than two package databases? What if I want to allow
multi-target support down the line, would I need package databases for
each target, or should they live in one package database and can share the
interface files while having different object files? I somewhat doubt that
would be practical generic solution due to cpp and architecture
differences?
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/11293#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list