This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Missing warning opportunity - code after break;

From: Soul Studios <matt at soulstudios dot co dot nz>
To: Eric Gallager <egall at gwmail dot gwu dot edu>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 22 Jun 2017 11:21:59 +1200
Subject: Re: Missing warning opportunity - code after break;
Authentication-results: sourceware.org; auth=none
References: <1343b3de-82e8-af4c-d8f9-7da385580c6d@soulstudios.co.nz> <CAMfHzOtn==_2jpLUh6=Kcg4pVz1QRvHm38gwf+4FJhDGiOm0Zw@mail.gmail.com>

Doesn't look like I can create a GCC bugzilla account, but 7 years? Wow.


On 20/06/2017 3:48 p.m., Eric Gallager wrote:

On 6/19/17, Soul Studios <matt@soulstudios.co.nz> wrote:

Just noticed this:
while(something)
{
	// stuff

	if (num_elements == 0)
	{
		break;
		--current_group;
	}
}

doesn't trigger a warning in GCC 5.1, 6.3 and 7.1. The line after
"break;" is unused, probably should be before the break, ie. user error.

Matt Bentley


This is bug 46476: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46476

References:
- Missing warning opportunity - code after break;
  - From: Soul Studios
- Re: Missing warning opportunity - code after break;
  - From: Eric Gallager

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]