public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/62138] New: Poor error recovery when parsing for-loops
@ 2014-08-14 16:12 manu at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: manu at gcc dot gnu.org @ 2014-08-14 16:12 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62138
Bug ID: 62138
Summary: Poor error recovery when parsing for-loops
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: manu at gcc dot gnu.org
This is the C version of PR62137:
manuel@gcc10:~$ cat parseerr.c
void foo(void)
{
for (int k, k < 20; k++);
}
manuel@gcc10:~$ ~/test1/213518M/build/gcc/cc1 parseerr.c -std=c99
parseerr.c: In function ‘foo’:
parseerr.c:3:17: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘<’ token
for (int k, k < 20; k++);
^
parseerr.c:3:26: error: expected ‘;’ before ‘)’ token
for (int k, k < 20; k++);
^
The first error doesn't make any sense.
>From gcc-bugs-return-458470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 14 16:14:41 2014
Return-Path: <gcc-bugs-return-458470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16625 invoked by alias); 14 Aug 2014 16:14:40 -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 16554 invoked by uid 55); 14 Aug 2014 16:14:34 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/62004] dead type-unsafe load replaces type-safe load
Date: Thu, 14 Aug 2014 16:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.8.4
X-Bugzilla-Keywords: patch, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vries at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-62004-4-2vIbnYeFlW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-62004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-62004-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/msg00967.txt.bz2
Content-length: 987
https://gcc.gnu.org/bugzilla/show_bug.cgi?idb004
--- Comment #5 from vries at gcc dot gnu.org ---
Author: vries
Date: Thu Aug 14 16:13:59 2014
New Revision: 213970
URL: https://gcc.gnu.org/viewcvs?rev!3970&root=gcc&view=rev
Log:
Fix if-conversion pass for dead type-unsafe code
2014-08-14 Tom de Vries <tom@codesourcery.com>
PR rtl-optimization/62004
PR rtl-optimization/62030
* ifcvt.c (rtx_interchangeable_p): New function.
(noce_try_move, noce_process_if_block): Use rtx_interchangeable_p.
* emit-rtl.c (mem_attrs_eq_p): Remove static.
* emit-rtl.h (mem_attrs_eq_p): Declare.
* gcc.dg/pr62004.c: New test.
* gcc.dg/pr62030.c: Same.
* gcc.target/mips/pr62030-octeon.c: Same.
Added:
trunk/gcc/testsuite/gcc.dg/pr62004.c
trunk/gcc/testsuite/gcc.dg/pr62030.c
trunk/gcc/testsuite/gcc.target/mips/pr62030-octeon.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/emit-rtl.h
trunk/gcc/ifcvt.c
trunk/gcc/testsuite/ChangeLog
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-08-14 16:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-14 16:12 [Bug c/62138] New: Poor error recovery when parsing for-loops 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).