diff options
author | peter <peter@FreeBSD.org> | 1996-09-18 05:35:50 +0000 |
---|---|---|
committer | peter <peter@FreeBSD.org> | 1996-09-18 05:35:50 +0000 |
commit | d4691e641ba47cb86eef80f5c879e13f9d961724 (patch) | |
tree | 5b7ea73fc49c8998d9dc87d3eeff5b96439e6856 /contrib/gcc/TESTS.FLUNK | |
download | FreeBSD-src-d4691e641ba47cb86eef80f5c879e13f9d961724.zip FreeBSD-src-d4691e641ba47cb86eef80f5c879e13f9d961724.tar.gz |
Import of unmodified (but trimmed) gcc-2.7.2. The bigger parts of the
non-i386, non-unix, and generatable files have been trimmed, but can easily
be added in later if needed.
gcc-2.7.2.1 will follow shortly, it's a very small delta to this and it's
handy to have both available for reference for such little cost.
The freebsd-specific changes will then be committed, and once the dust has
settled, the bmakefiles will be committed to use this code.
Diffstat (limited to 'contrib/gcc/TESTS.FLUNK')
-rw-r--r-- | contrib/gcc/TESTS.FLUNK | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/contrib/gcc/TESTS.FLUNK b/contrib/gcc/TESTS.FLUNK new file mode 100644 index 0000000..04641e3 --- /dev/null +++ b/contrib/gcc/TESTS.FLUNK @@ -0,0 +1,39 @@ +This is a collection of things that test suites have +said were "wrong" with GCC--but that I don't agree with. + +First, test suites sometimes test for compatibility with +traditional C. GCC with -traditional is not completely +compatible with traditional C, and in some ways I think it +should not be. + +* K&R C allowed \x to appear in a string literal (or character +literal?) even in cases where it is *not* followed by a sequence of +hex digits. I'm not convinced this is desirable. + +* K&R compilers allow comments to cross over an inclusion boundary (i.e. +started in an include file and ended in the including file). +I think this would be quite ugly and can't imagine it could +be needed. + +Sometimes tests disagree with GCC's interpretation of the ANSI standard. + +* One test claims that this function should return 1. + + enum {A, B} foo; + + func (enum {B, A} arg) + { + return B; + } + +I think it should return 0, because the definition of B that +applies is the one in func. + +* Some tests report failure when the compiler does not produce +an error message for a certain program. + +ANSI C requires a "diagnostic" message for certain kinds of invalid +programs, but a warning counts as a diagnostic. If GCC produces +a warning but not an error, that is correct ANSI support. +When test suites call this "failure", the tests are broken. + |