From: Joseph Myers <joseph@codesourcery.com>
To: Richard Biener <rguenther@suse.de>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][gimplefe] Improve error recovery
Date: Tue, 20 Dec 2016 17:26:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1612201720330.10818@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LSU.2.11.1612200948360.5294@t29.fhfr.qr>
On Tue, 20 Dec 2016, Richard Biener wrote:
> Just noticed a few issues when feeding the GIMPLE FE random -gimple
> dumps. On errors not skipping to expected tokens leads to a load
> of strange followup parsing errors and worse, to endless parsing
> attempts in one case.
>
> Fixed with the following.
>
> Bootstrap / regtest running together with the pass manager change
> posted in the other thread.
>
> I consider gimple-parser.c changes like this "middle-end", Joseph,
> are you fine with that?
I'm fine with that.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2016-12-20 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 8:57 Richard Biener
2016-12-20 17:26 ` Joseph Myers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1612201720330.10818@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).