--- /dev/null
+2002-06-24 Andrew Birkett <adb@tardis.ed.ac.uk>
+
+ * fail: cs0121.cs, cs0157.cs and cs1501.cs no longer fail.
+ * cs0176.cs: Method has to be public for correct test
+ * cs0196.cs, cs0242.cs: Do 'return' to stop null statement warning.
+ * cs0255.cs: Add assignment to stop 'unused variable' warning.
+ * makefile: Output is now like "Running test 42 .. OK". Added --unsafe to
+ make cs0193.cs, cs0196.cs and cs0214-3.cs work.
+
The following tests failed:
-cs0051.cs, cs0060.cs, cs0111.cs
-
+cs0051.cs: We don't complain about inconsistent accessibility.
+cs0060.cs: We don't complain about inconsistent accessibility.
cs0108.cs: We should re-enable the test code in the compiler
cs0110.cs: Stack overflow in the compiler
-
-cs0118.cs:
- We report the error, but the CSC error gives more information.
-
-cs0121.cs: Function deambiguator does not work here
-cs0136-2.cs cs0136.cs: Similar error reported (reuse of variable name, 128)
-cs0157.cs: Internal compiler error (null pointer reference)
+cs0111.cs: We don't complain about second occurance of method definition.
+cs0118.cs: We report the error, but the CSC error gives more information.
+cs0136.cs: Similar error reported (reuse of variable name, 128)
+cs0136-2.cs: Similar error reported (reuse of variable name, 128)
cs0164.cs: We dont emit the warning for an unused label
-cs0165-2.cs cs0165.cs:
- We need data flow analysis
-
-cs0171.cs
- We do not track unassigned struct fields on struct constructors
-
-cs0216.cs:
- We do not report missing operators.
-
-cs0234.cs:
- Will be hard to fix;
-
-cs0654.cs:
- Compiler crash
-
-cs1001.cs:
- Compiler emits syntax error; Its ok.
-
- Compiler crashes
-cs1501.cs:
- Compiler crashes. Easy to fix
-
-cs1513.cs:
- Syntax error; We could provide better message
-
-cs1518.cs:
- Syntax error; We could provide better message
-
-cs1525.cs:
- Syntax error; We could provide better message
-
-cs1528.cs:
- Syntax error; We could provide better message
-
-cs1529.cs:
- Syntax error; We could provide better message
+cs0165.cs: We need data flow analysis
+cs0165-2.cs: We need data flow analysis
+cs0171.cs: We do not track unassigned struct fields on struct constructors
+cs0216.cs: We do not report missing operators.
+cs0234.cs: Will be hard to fix;
+cs0255.cs: Error isn't flagged.
+cs0523.cs: Error isn't flagged.
+cs0529.cs: We get error CS0146 instead
+cs0654.cs: Compiler crash
+cs1001.cs: Compiler emits syntax error; Its ok.
+cs1513.cs: Syntax error; We could provide better message
+cs1518.cs: Syntax error; We could provide better message
+cs1525.cs: Syntax error; We could provide better message
+cs1528.cs: Syntax error; We could provide better message
+cs1529.cs: Syntax error; We could provide better message
+cs1552.cs: Syntax error; We could provide better message
+cs1604.cs: Error isn't flagged.
+cs-20.cs: Attribute error isn't flagged
-cs1552.cs:
- Syntax error; We could provide better message
#
# Compile at the maximum warning level to probe for warnings
#
-MCS=../mcs/mcs.exe --wlevel 4
+#MCS=mono ../mcs/mcs.exe --wlevel 4 # for linux
+MCS=../mcs/mcs.exe --wlevel 4 # for windows
+
all:
- failed=false; \
+ @ failed=false; \
for i in cs*.cs; do \
case $$i in \
cs[0-9]*-[0-9]*cs) \
error=`echo $$i | sed -e 's/cs*//' -e 's/.cs//'`; \
;;\
esac; \
- echo $(MCS) --probe $$error $$i; \
- $(MCS) --probe $$error 1 $$i > /dev/null; \
- code=$$?; \
- if test $$code != 123; then \
- echo Code is: $$code; \
- if [ x$$code = x124 ]; then \
- echo "Compiler failed to flag $$i"; \
- else \
- echo "Compiler failed to compile $$i"; \
- fi; \
- flist="$$flist $$i"; \
- failed=true; \
- else \
- echo test $$i ok; \
+ echo -n "Running test $$i ... "; \
+ if $(MCS) --unsafe --expect-error $$error $$i > /dev/null; \
+ then echo OK; \
+ else echo FAILED; \
+ flist="$$flist $$i"; \
+ failed=true; \
fi; \
done; \
if $$failed; then \