http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202
--- Comment #8 from Manuel López-Ibáñez 2011-09-29
20:54:46 UTC ---
(In reply to comment #4)
> Manuel, do you have an opinion about this rather old issue? In the meanwhile,
> the warning became an hard error, when it applies. Thus the original te
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202
--- Comment #7 from Jonathan Wakely 2011-09-29
17:26:57 UTC ---
To the OP, you've probably fixed it by now, but you must have a varargs
function with ... somewhere, or you wouldn't get the error. You could add a
conflicting declaration which woul
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202
Paolo Carlini changed:
What|Removed |Added
CC|gcc-bugs at gcc dot gnu.org |
--- Comment #6 from Paolo Carlini 2011-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202
--- Comment #5 from Jonathan Wakely 2011-09-29
16:16:48 UTC ---
(In reply to comment #4)
> In the meanwhile,
> the warning became an hard error, when it applies.
It went from "undefined" to "conditionally-supported" behaviour in C++11
> ICC war
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202
Paolo Carlini changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Comment #4 fr
