Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: mwoehlke.floss at gmail dot com
Target Milestone: ---
While trying to fix warnings in a code base, we noticed that some are very
strange:
foo.cpp: warning: by ‘virtual ...’ [-Werror=overloaded-virtual]
bar.cpp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52718
--- Comment #16 from mwoehlke.floss at gmail dot com 2012-11-01 22:03:46 UTC ---
On 2012-11-01 16:52, paolo.carlini at oracle dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52718
> --- Comment #15 from Paolo Carlini
iority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: mwoehlke.floss at gmail dot com
Target Milestone: ---
Consider the following code:
int foo()
{
for (int y = 0; !y;)
for (/*decl*/; !y; ++y)
return 1;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67629
--- Comment #8 from Matthew Woehlke ---
Given what -Wreturn-type is trying to accomplish, I wonder if a "delayed
issuance" strategy would be in order? IOW, have the front end "trigger" the
warning, as now, but stuff it in a queue or such, continu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7652
--- Comment #37 from Matthew Woehlke ---
> Essentially, this warning and the "intentional fallthrough" attribute
exist for both clang and MSVC and will be enabled there; but GCC
still doesn't have this feature.
[[fallthrough]] was approved for C+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7652
--- Comment #39 from Matthew Woehlke ---
(In reply to Jonathan Wakely from comment #38)
> (In reply to Matthew Woehlke from comment #37)
> > [[fallthrough]] was approved for C++17 [...] It's a shame that gcc is behind
> > the curve here.
>
> It w
