[AArch64 costs 10/18] Improve costs for sign/zero extend operations

[gcc.git] / fixincludes / README

diff --git a/fixincludes/README b/fixincludes/README
index 07a3964a26aaaf082c7bb996d32d93f348bd335c..9b482102b285248d2b8b1ae14c5ef3dff6199519 100644 (file)
--- a/fixincludes/README
+++ b/fixincludes/README
@@ -44,6 +44,9 @@ To make your fix, you will need to do several things:
     Make sure it is now properly handled.  Add tests to the
     "test_text" entry(ies) that validate your fix.  This will
     help ensure that future fixes won't negate your work.
+    Do *NOT* specify test text for "wrap" or "replacement" fixes.
+    There is no real possibility that these fixes will fail.
+    If they do, you will surely know straight away.
 
 5.  Go into the fixincludes build directory and type, "make check".
     You are guaranteed to have issues printed out as a result.
@@ -314,7 +317,7 @@ EXAMPLES OF FIXES:
     GCC.  But you can also:
 
         cd ${top_builddir}/gcc
-        rm -rf fixinc.sh include/ stmp-fixinc
+        rm -rf include-fixed/ stmp-fixinc
         make stmp-fixinc
 
     I would really recommend, however: