X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fusing.xml;h=115c290491f97c61f766e70ef4f35636c2180502;hb=3bb700d515de2405fa5db3326482e529f332d508;hp=ed08f58ebc23437d6b3bdc3c8be176bb7e912e38;hpb=7eb9cce3caca822cbbe1fa3a31ff0b4e0df3c369;p=ghc-hetmet.git
diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml
index ed08f58..115c290 100644
--- a/docs/users_guide/using.xml
+++ b/docs/users_guide/using.xml
@@ -1300,6 +1300,39 @@ f foo = foo { x = 6 }
+
+ :
+
+ missing import lists, warning
+ import lists, missing
+
+
+
+ This flag warns if you use an unqualified
+ import declaration
+ that does not explicitly list the entities brought into scope. For
+ example
+
+
+module M where
+ import X( f )
+ import Y
+ import qualified Z
+ p x = f x x
+
+
+ The flag will warn about the import
+ of Y but not X
+ If module Y is later changed to export (say) f,
+ then the reference to f in M will become
+ ambiguous. No warning is produced for the import of Z
+ because extending Z's exports would be unlikely to produce
+ ambiguity in M.
+
+
+
+
+ :
@@ -1340,6 +1373,20 @@ f foo = foo { x = 6 }
+ :
+
+
+ type signatures, missing
+
+ If you use the
+ flag GHC will warn
+ you about any polymorphic local bindings. As part of
+ the warning GHC also reports the inferred type. The
+ option is off by default.
+
+
+
+ :
@@ -1668,7 +1715,7 @@ f "2" = 2
We don't use a flag for day-to-day
work. We use to get respectable speed;
e.g., when we want to measure something. When we want to go for
- broke, we tend to use (and we go for
+ broke, we tend to use (and we go for
lots of coffee breaks).The easiest way to see what (etc.)
@@ -2112,25 +2159,6 @@ f "2" = 2
-
-
- RTS
- option
-
- Migrate a thread to the current CPU when it is woken
- up. Normally when a thread is woken up after being
- blocked it will be scheduled on the CPU it was running on
- last; this option allows the thread to immediately migrate
- to the CPU that unblocked it.
-
- The rationale for allowing this eager migration is
- that it tends to move threads that are communicating with
- each other onto the same CPU; however there are
- pathalogical situations where it turns out to be a poor
- strategy. Depending on the communication pattern in your
- program, it may or may not be a good idea.
-
-
@@ -2189,27 +2217,6 @@ f "2" = 2
-
- :
-
- (x86 only)-monly-N-regs
- option (iX86 only) GHC tries to
- “steal” four registers from GCC, for performance
- reasons; it almost always works. However, when GCC is
- compiling some modules with four stolen registers, it will
- crash, probably saying:
-
-
-Foo.hc:533: fixed or forbidden register was spilled.
-This may be due to a compiler bug or to impossible asm
-statements or clauses.
-
-
- Just give some registers back with
- . Try `3' first, then `2'.
- If `2' doesn't work, please report the bug to us.
-
-