diff options
author | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
---|---|---|
committer | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
commit | 554fd8c5195424bdbcabf5de30fdc183aba391bd (patch) | |
tree | 976dc5ab7fddf506dadce60ae936f43f58787092 /gcc/testsuite/g++.dg/template/error10.C | |
download | cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.bz2 cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.xz |
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.
downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.
if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.
Diffstat (limited to 'gcc/testsuite/g++.dg/template/error10.C')
-rw-r--r-- | gcc/testsuite/g++.dg/template/error10.C | 71 |
1 files changed, 71 insertions, 0 deletions
diff --git a/gcc/testsuite/g++.dg/template/error10.C b/gcc/testsuite/g++.dg/template/error10.C new file mode 100644 index 000000000..02ea64b79 --- /dev/null +++ b/gcc/testsuite/g++.dg/template/error10.C @@ -0,0 +1,71 @@ +// { dg-do compile } +// { dg-options "-std=gnu++98" } +// Origin: <tilps at hotmail dot com> +// c++/9154: poor error message for ">>" vs "> >" in template argument list + + +/* + * Test that the error message is issued properly + */ +template <class T> +class A {}; + +A<A<int>> blah; // { dg-error "should be '> >' within" } +A<int>> blah2; // { dg-error "spurious '>>'" } + + +/* + * Test that a few valid constructs containing a ">>" token in a + * template argument list are handled correctly. + */ +template <int N> +void B(void) {} + +int Btest() +{ + B<256 >> 4>(); +} + +template <int N = 123>>4> +struct C {}; + +template <int> struct D {}; +template <typename> struct E {}; + +E<D< 1>>2 > > E1; + +const int x = 0; +E<D< 1>>x > > E2; + +template <int> struct F { + typedef int I; +}; + +template <typename T = F< 1>>2 >::I> +struct G {}; + +/* + * In this special case, a valid type-id (H() is a function type) is followed + * by '>>', but the argument should still be parsed as an expression, which + * will then be rejected as non-constant expression. + */ +struct H +{ + int operator >>(int); +}; + +template <int V> struct L {}; +L<H() >> 5> l; // { dg-error "" "non-constant" } + + +/* + * This case used to not emit the nice error message because of a typo + * in the code. + */ +template <void (*)(void)> +struct K {}; + +void KFunc(void); + +A<K<&KFunc>> k1; // { dg-error "" } +K<&KFunc>> k2; // { dg-error "" } |