summaryrefslogtreecommitdiffstats
path: root/fixincludes/README
diff options
context:
space:
mode:
authorkorbb <korbb@138bc75d-0d04-0410-961f-82ee72b054a4>2012-10-29 16:44:34 +0000
committerkorbb <korbb@138bc75d-0d04-0410-961f-82ee72b054a4>2012-10-29 16:44:34 +0000
commit32f37500f7c19b59875ef53443a7a3a48fc6a865 (patch)
tree041ab47b1a5538f005ec95ec88d8276481253110 /fixincludes/README
parent3190d74b90c0afec47b26cc43afe04126ee0fd84 (diff)
downloadppe42-gcc-32f37500f7c19b59875ef53443a7a3a48fc6a865.tar.gz
ppe42-gcc-32f37500f7c19b59875ef53443a7a3a48fc6a865.zip
Omit testing wrap and replacement fixes during testing.
This exposes a missing result and tests a test that got hidden before. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@192952 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'fixincludes/README')
-rw-r--r--fixincludes/README3
1 files changed, 3 insertions, 0 deletions
diff --git a/fixincludes/README b/fixincludes/README
index c7144a0ba29..9b482102b28 100644
--- 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.
OpenPOWER on IntegriCloud