https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
Wolfgang Bangerth changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
--- Comment #12 from Andrew Pinski ---
Since GCC 11 we produce:
: In function 'void g()':
:7:4: error: no matching function for call to 'f(int [])'
7 | f( buf ) ;
| ~^~~
:3:28: note: candidate: 'template void f(int (&)[N])'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
Martin Sebor changed:
What|Removed |Added
Priority|P2 |P3
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
--- Comment #10 from Gabriel Dos Reis 2013-04-23
03:45:56 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > Printing int[] or int[size_t] would be confusing too.
>
> More confusing than int[(((sizetype)) + 1)] ?
>
> What about?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
--- Comment #9 from Manuel López-Ibáñez 2013-04-22
10:38:05 UTC ---
(In reply to comment #8)
> Printing int[] or int[size_t] would be confusing too.
More confusing than int[(((sizetype)) + 1)] ?
What about?
t7881.cc: In function ‘void g()’:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
--- Comment #8 from Gabriel Dos Reis 2013-04-22
10:10:36 UTC ---
(In reply to comment #7)
> The '[(((sizetype)) + 1)]' is just awful. If we don't know the
> actual type there, that is "int [size()]", then we should just print 'int []'
> o
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11582
--- Comment #6 from Andrew Pinski 2012-02-02
00:30:07 UTC ---
t788.cc: In function ‘void g()’:
t788.cc:6:10: error: no matching function for call to ‘f(int
[(((sizetype)) + 1)])’
t788.cc:6:10: note: candidate is:
t788.cc:2:28: note: template void
