From: Prathamesh Kulkarni <bilbotheelffriend@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>,
Diego Novillo <dnovillo@google.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Re: [gsoc][match-and-simplify] allow multiple patterns inside for ?
Date: Tue, 22 Jul 2014 22:27:00 -0000 [thread overview]
Message-ID: <CAJXstsAHYHiRpm1MHWWMedWG0hrfZH0CmOoJdtTmbsoW7K4Nag@mail.gmail.com> (raw)
In-Reply-To: <CAJXstsDiLAin+5vq_wTL1N0vzGLz5SNqBfgkQMYSCONQHcoL_Q@mail.gmail.com>
On Wed, Jul 23, 2014 at 3:42 AM, Prathamesh Kulkarni
<bilbotheelffriend@gmail.com> wrote:
> Would it be a good idea to allow multiple match_and_simplify within for ?
allow multiple patterns (match_and_simplify, for).
> * genmatch.c (parse_for): Adjust to parse multiple patterns.
>
> Thanks and Regards,
> Prathamesh
next prev parent reply other threads:[~2014-07-22 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 22:14 Prathamesh Kulkarni
2014-07-22 22:27 ` Prathamesh Kulkarni [this message]
2014-07-23 9:18 ` Richard Biener
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=CAJXstsAHYHiRpm1MHWWMedWG0hrfZH0CmOoJdtTmbsoW7K4Nag@mail.gmail.com \
--to=bilbotheelffriend@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=richard.guenther@gmail.com \
/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).