summaryrefslogtreecommitdiff
path: root/compiler/prelude/PrelInfo.lhs
Commit message (Collapse)AuthorAgeFilesLines
* Added a VECTORISE pragmaManuel M T Chakravarty2011-02-201-11/+11
| | | | | | | | | | | | | | | - Added a pragma {-# VECTORISE var = exp #-} that prevents the vectoriser from vectorising the definition of 'var'. Instead it uses the binding '$v_var = exp' to vectorise 'var'. The vectoriser checks that the Core type of 'exp' matches the vectorised Core type of 'var'. (It would be quite complicated to perform that check in the type checker as the vectorisation of a type needs the state of the VM monad.) - Added parts of a related VECTORISE SCALAR pragma - Documented -ddump-vect - Added -ddump-vt-trace - Some clean up
* Move error-ids to MkCore (from PrelRules)simonpj@microsoft.com2010-09-141-2/+3
| | | | and adjust imports accordingly
* Remove GHC's haskell98 dependencyIan Lynagh2009-07-241-1/+1
|
* Fixes for haddock 0.8Ian Lynagh2008-07-211-1/+1
|
* PrelInfo is now warning-freeIan Lynagh2008-04-131-7/+2
|
* Fix CodingStyle#Warnings URLsIan Lynagh2007-09-041-1/+1
|
* Use OPTIONS rather than OPTIONS_GHC for pragmasIan Lynagh2007-09-031-2/+2
| | | | | | | Older GHCs can't parse OPTIONS_GHC. This also changes the URL referenced for the -w options from WorkingConventions#Warnings to CodingStyle#Warnings for the compiler modules.
* Add {-# OPTIONS_GHC -w #-} and some blurb to all compiler modulesIan Lynagh2007-09-011-0/+7
|
* Remove Linear Implicit Parameters, and all their workssimonpj@microsoft.com2006-09-291-1/+0
| | | | | | | Linear implicit parameters have been in GHC quite a while, but we decided they were a mis-feature and scheduled them for removal. This patch does the job.
* Massive patch for the first months work adding System FC to GHC #28Manuel M T Chakravarty2006-08-041-0/+3
| | | | | | | | Broken up massive patch -=chak Original log message: This is (sadly) all done in one patch to avoid Darcs bugs. It's not complete work... more FC stuff to come. A compiler using just this patch will fail dismally.
* Do not put wired-in things in interface filessimonpj@microsoft.com2006-05-081-2/+18
| | | | | | | | | | | | | | | There is no need for wired-in things to go into interface files; the compiler knows about them anyway. Worse, it turns ou that if they are in an interface file, they may get read in with not-quite-right type info (e.g. GHC.Err.error), and the not-quite-right thing gets into the type envt. Than it gets used instead of the wired in thing. Best all round never to put them into interface files. This is the way it used to be, but it looks as if it rotted away some time ago. (I noticed this when fixing unsafePerformIO stuff, becuase 'lazy' was getting an unfolding when it shouldn't.)
* Reorganisation of the source treeSimon Marlow2006-04-071-0/+139
Most of the other users of the fptools build system have migrated to Cabal, and with the move to darcs we can now flatten the source tree without losing history, so here goes. The main change is that the ghc/ subdir is gone, and most of what it contained is now at the top level. The build system now makes no pretense at being multi-project, it is just the GHC build system. No doubt this will break many things, and there will be a period of instability while we fix the dependencies. A straightforward build should work, but I haven't yet fixed binary/source distributions. Changes to the Building Guide will follow, too.