[Bug c/62184] New: [C/C++] Extend -Wempty-body to

public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed

* [Bug c/62184] New: [C/C++] Extend -Wempty-body to
@ 2014-08-19  9:50 burnus at gcc dot gnu.org
  2014-08-19  9:53 ` [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops burnus at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: burnus at gcc dot gnu.org @ 2014-08-19  9:50 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62184

            Bug ID: 62184
           Summary: [C/C++] Extend -Wempty-body to
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops
  2014-08-19  9:50 [Bug c/62184] New: [C/C++] Extend -Wempty-body to burnus at gcc dot gnu.org
@ 2014-08-19  9:53 ` burnus at gcc dot gnu.org
  2014-08-21  1:13 ` manu at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: burnus at gcc dot gnu.org @ 2014-08-19  9:53 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62184

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
                 CC|                            |mpolacek at gcc dot gnu.org
            Summary|[C/C++] Extend -Wempty-body |[C/C++] Extend -Wempty-body
                   |to                          |to 'while' loops

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
For an empty "if" loop, GCC warns with -Wextra:

foo.cc:5:13: warning: suggest braces around empty body in an ‘if’ statement
[-Wempty-body]
   if (bar());
             ^


However, using a "while" loop, it doesn't. Clang warns (by default) in that
case:

foo.cc:5:16: warning: while loop has empty body [-Wempty-body]
  while (bar());
               ^
foo.cc:5:16: note: put the semicolon on a separate line to silence this warning


Again, I found that issue in a real-world code.

Test case:

int bar ();
void sleep();

int foo() {
  while (bar());
    sleep();
  return 1;
}
>From gcc-bugs-return-458765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 19 09:53:28 2014
Return-Path: <gcc-bugs-return-458765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2648 invoked by alias); 19 Aug 2014 09:53:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2581 invoked by uid 48); 19 Aug 2014 09:53:24 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/62183] [C/C++] Warning wished for "!int_val == const" / logical not is only applied to the left hand side of this comparison
Date: Tue, 19 Aug 2014 09:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-62183-4-4vsdE5RLnW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-62183-4@http.gcc.gnu.org/bugzilla/>
References: <bug-62183-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01262.txt.bz2
Content-length: 518

https://gcc.gnu.org/bugzilla/show_bug.cgi?idb183

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I implemented -Wlogical-not-parentheses a while ago.  It's not in -Wall yet
though, see PR61271.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops
  2014-08-19  9:50 [Bug c/62184] New: [C/C++] Extend -Wempty-body to burnus at gcc dot gnu.org
  2014-08-19  9:53 ` [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops burnus at gcc dot gnu.org
@ 2014-08-21  1:13 ` manu at gcc dot gnu.org
  2014-08-21  7:48 ` burnus at gcc dot gnu.org
  2014-11-12 15:26 ` manu at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: manu at gcc dot gnu.org @ 2014-08-21  1:13 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62184

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
We had this and it got removed (see PR36478). Perhaps a better implementation
is possible now that we track macro locations.

(I wonder how the Clang guys get away with warning about all this stuff by
default. Is it because they have very good heuristics to avoid being annoying?)
>From gcc-bugs-return-458931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 21 01:23:57 2014
Return-Path: <gcc-bugs-return-458931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29397 invoked by alias); 21 Aug 2014 01:23:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29339 invoked by uid 48); 21 Aug 2014 01:23:51 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/7652] -Wswitch-break : Warn if a switch case falls through
Date: Thu, 21 Aug 2014 01:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-7652-4-s9QFqiunA2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-7652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-7652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01428.txt.bz2
Content-length: 257

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7652

--- Comment #34 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
In any case, the current patch needs more work. In case you want to see this in
GCC 5.0, you need to hurry up! :)
>From gcc-bugs-return-458932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 21 01:24:32 2014
Return-Path: <gcc-bugs-return-458932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30155 invoked by alias); 21 Aug 2014 01:24:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30123 invoked by uid 48); 21 Aug 2014 01:24:28 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/7651] Define -Wextra strictly in terms of other warning flags
Date: Thu, 21 Aug 2014 01:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-7651-4-YHsm13J2IZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-7651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-7651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01429.txt.bz2
Content-length: 393

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7651

--- Comment #28 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
A good way to finish this is to find which option in Clang warns for the
corresponding thing in Wextra and add the same option to GCC.

I can take care of writing and testing the patches but someone else would need
to do the search for each warning.
>From gcc-bugs-return-458933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 21 02:01:03 2014
Return-Path: <gcc-bugs-return-458933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9598 invoked by alias); 21 Aug 2014 02:01:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8025 invoked by uid 48); 21 Aug 2014 02:00:48 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44786] -fsanitize=undefined: Turn on runtime code generation to check for undefined behavior
Date: Thu, 21 Aug 2014 02:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-44786-4-iRwzhiAlbz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01430.txt.bz2
Content-length: 386

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44786

--- Comment #11 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Manuel López-Ibáñez from comment #10)
> So what is missing here? Can we close this or not yet?

I've tested that -fno-sanitize-recover works correctly with gcc-snapshot under
Debian. So, I suppose that this can be closed.
>From gcc-bugs-return-458934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 21 02:12:08 2014
Return-Path: <gcc-bugs-return-458934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28398 invoked by alias); 21 Aug 2014 02:12:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24455 invoked by uid 48); 21 Aug 2014 02:11:52 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/44521] unhelpful candidates for ambiguous lookup
Date: Thu, 21 Aug 2014 02:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-44521-4-33ufSdEBHI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01431.txt.bz2
Content-length: 850

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44521

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-08-21
     Ever confirmed|0                           |1

--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #1)
> Jason, do we want this?
> 
> Following Clang or in some other way?

Yes, the Clang diagnostic is better.

There are two issues with the G++ diagnostic:

1) It talks about f(double), which is not viable.
2) It doesn't distinguish between two occurrences of the same function reached
through different base paths.
>From gcc-bugs-return-458935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 21 02:13:53 2014
Return-Path: <gcc-bugs-return-458935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31726 invoked by alias); 21 Aug 2014 02:13:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31641 invoked by uid 48); 21 Aug 2014 02:13:43 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60417] [DR 1518] Bogus error on C++03 aggregate initialization
Date: Thu, 21 Aug 2014 02:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-60417-4-gPT6C9R6hB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01432.txt.bz2
Content-length: 488

https://gcc.gnu.org/bugzilla/show_bug.cgi?id`417

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |4.9.2

--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 4.9.2.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops
  2014-08-19  9:50 [Bug c/62184] New: [C/C++] Extend -Wempty-body to burnus at gcc dot gnu.org
  2014-08-19  9:53 ` [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops burnus at gcc dot gnu.org
  2014-08-21  1:13 ` manu at gcc dot gnu.org
@ 2014-08-21  7:48 ` burnus at gcc dot gnu.org
  2014-11-12 15:26 ` manu at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: burnus at gcc dot gnu.org @ 2014-08-21  7:48 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62184

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #2)
> We had this and it got removed (see PR36478). Perhaps a better
> implementation is possible now that we track macro locations.

There one had:
warn2.cc:6: error: suggest a space before ‘;’ or explicit braces around empty

While CLANG requires a new line (according to the message), such that
#define EMPTY
  while()
    EMPTY;
would be fine while
  while(f()) ; // or: while(f())EMPTY;
wouldn't. (Given how stray spaces enter the code, I'd also like the "while(f())
;" warning.)


> (I wonder how the Clang guys get away with warning about all this stuff by
> default. Is it because they have very good heuristics to avoid being
> annoying?)

Me too, although I have a log file here with "clang -Weverything" for our code,
from which I extract all warning classes (164M) - and look at the individual
warnings for those looking potentially interesting. [BTW: One should also
consider adding -Weverything to GCC, which helps to find discover warning
options.]
>From gcc-bugs-return-458943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 21 07:49:25 2014
Return-Path: <gcc-bugs-return-458943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19259 invoked by alias); 21 Aug 2014 07:49:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19239 invoked by uid 48); 21 Aug 2014 07:49:21 -0000
From: "tony.wang at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/62213] New: [5 Rgression] ICE in lto for test case 20081120-1
Date: Thu, 21 Aug 2014 07:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tony.wang at arm dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-62213-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg01440.txt.bz2
Content-length: 3020

https://gcc.gnu.org/bugzilla/show_bug.cgi?idb213

            Bug ID: 62213
           Summary: [5 Rgression] ICE in lto for test case 20081120-1
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tony.wang at arm dot com

Run into a lto test case ICE on trunk.

/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/xgcc
-B/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/
-fno-diagnostics-show-caret -fdiagnostics-color=never  -flto -r -nostdlib  -c
 -mthumb -mcpu=cortex-m0  -o c_lto_20081120-1_0.o
/home/build/work/GCC-5-0-build/src/gcc/gcc/testsuite/gcc.dg/lto/20081120-1_0.c
/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/xgcc
-B/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/
-fno-diagnostics-show-caret -fdiagnostics-color=never  -flto -r -nostdlib  -c
 -mthumb -mcpu=cortex-m0  -o c_lto_20081120-1_1.o
/home/build/work/GCC-5-0-build/src/gcc/gcc/testsuite/gcc.dg/lto/20081120-1_1.c
/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/xgcc
-B/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/
c_lto_20081120-1_0.o c_lto_20081120-1_1.o gcc_tg.o  -fno-diagnostics-show-caret
-fdiagnostics-color=never  -flto -r -nostdlib       -Wl,-wrap,exit
-Wl,-wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort     -mthumb -mcpu=cortex-m0  -o
gcc-dg-lto-20081120-1-01.exe

lto1: internal compiler error: in do_whole_program_analysis, at
lto/lto.c:3249^M
0x81b8acf do_whole_program_analysis^M
        /home/build/work/GCC-5-0-build/src/gcc/gcc/lto/lto.c:3249^M
0x81b8acf lto_main()^M
        /home/build/work/GCC-5-0-build/src/gcc/gcc/lto/lto.c:3427^M
Please submit a full bug report,^M
with preprocessed source if appropriate.^M
Please include the complete backtrace with any bug report.^M
See <http://gcc.gnu.org/bugs.html> for instructions.^M
lto-wrapper: fatal error:
/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/xgcc returned 1 exit
status^M
compilation terminated.^M
/home/build/work/GCC-5-0-build/install-native/arm-none-eabi/bin/ld: lto-wrapper
failed^M
collect2: error: ld returned 1 exit status^M
compiler exited with status 1
output is:
lto1: internal compiler error: in do_whole_program_analysis, at
lto/lto.c:3249^M
0x81b8acf do_whole_program_analysis^M
        /home/build/work/GCC-5-0-build/src/gcc/gcc/lto/lto.c:3249^M
0x81b8acf lto_main()^M
        /home/build/work/GCC-5-0-build/src/gcc/gcc/lto/lto.c:3427^M
Please submit a full bug report,^M
with preprocessed source if appropriate.^M
Please include the complete backtrace with any bug report.^M
See <http://gcc.gnu.org/bugs.html> for instructions.^M
lto-wrapper: fatal error:
/home/build/work/GCC-5-0-build/build-native/gcc-final/gcc/xgcc returned 1 exit
status^M
compilation terminated.^M
/home/build/work/GCC-5-0-build/install-native/arm-none-eabi/bin/ld: lto-wrapper
failed^M
collect2: error: ld returned 1 exit status^M


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops
  2014-08-19  9:50 [Bug c/62184] New: [C/C++] Extend -Wempty-body to burnus at gcc dot gnu.org
                   ` (2 preceding siblings ...)
  2014-08-21  7:48 ` burnus at gcc dot gnu.org
@ 2014-11-12 15:26 ` manu at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: manu at gcc dot gnu.org @ 2014-11-12 15:26 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62184

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-11-12
     Ever confirmed|0                           |1

--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
I'm going to confirm this. We definitely want this. The heuristic of Clang
seems quite elaborated: only warn when the ';' is on the same line and there is
a statement after it that starts at a higher column than the while.line.

void foo ()
{
#define EMPTY
  while (0)EMPTY;
    foo(); // warns if preprocessed
  while (0);
   foo(); // warns
  while (0);
  foo(); // does not warn
  while (0); // does not warn
}

$ clang test.c 
test.c:6:12: warning: while loop has empty body [-Wempty-body]
  while (0);
           ^
test.c:6:12: note: put the semicolon on a separate line to silence this warning

$ clang test.c -save-temps
In file included from test.c:1:
test.c:4:12: warning: while loop has empty body [-Wempty-body]
  while (0);
           ^
test.c:4:12: note: put the semicolon on a separate line to silence this warning
test.c:6:12: warning: while loop has empty body [-Wempty-body]
  while (0);
           ^
test.c:6:12: note: put the semicolon on a separate line to silence this warning
>From gcc-bugs-return-466533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 12 15:29:36 2014
Return-Path: <gcc-bugs-return-466533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10698 invoked by alias); 12 Nov 2014 15:29:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10672 invoked by uid 48); 12 Nov 2014 15:29:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/63832] [5.0 Regression] crtstuff.c:400:19: warning: array subscript is above array bounds [-Warray-bounds]
Date: Wed, 12 Nov 2014 15:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-63832-4-3CAcASFJw7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg01005.txt.bz2
Content-length: 352

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc832

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
   Target Milestone|---                         |5.0


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-11-12 15:26 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-19  9:50 [Bug c/62184] New: [C/C++] Extend -Wempty-body to burnus at gcc dot gnu.org
2014-08-19  9:53 ` [Bug c/62184] [C/C++] Extend -Wempty-body to 'while' loops burnus at gcc dot gnu.org
2014-08-21  1:13 ` manu at gcc dot gnu.org
2014-08-21  7:48 ` burnus at gcc dot gnu.org
2014-11-12 15:26 ` manu at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).