From: Richard Biener <richard.guenther@gmail.com>
To: Prathamesh Kulkarni <bilbotheelffriend@gmail.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: [gsoc 2014] moving fold-const patterns to gimple
Date: Mon, 17 Mar 2014 08:52:00 -0000 [thread overview]
Message-ID: <CAFiYyc2dwsfrS=69bNw0JGBeJY4krM--Q0FUMmkup2pVvJ2YMA@mail.gmail.com> (raw)
In-Reply-To: <CAJXstsDnSn54JNVaN3ZY8b4LnfjgYJ=0p_+M+_GnYVTF3-NMrA@mail.gmail.com>
On Sun, Mar 16, 2014 at 1:21 PM, Prathamesh Kulkarni
<bilbotheelffriend@gmail.com> wrote:
> In c_expr::c_expr, shouldn't OP_C_EXPR be passed to operand
> constructor instead of OP_EXPR ?
Indeed - I have committed the fix.
Thanks,
Richard.
> This caused segfault for patterns when "simplification" operand was
> only c_expr (patch attached).
>
> * genmatch.c (c_expr::c_expr): use OP_C_EXPR instead of OP_EXPR in
> call to operand constructor.
next prev parent reply other threads:[~2014-03-17 8:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 20:13 Prathamesh Kulkarni
2014-03-03 10:02 ` Richard Biener
2014-03-06 12:11 ` Prathamesh Kulkarni
2014-03-06 12:43 ` Richard Biener
2014-03-06 18:17 ` Prathamesh Kulkarni
2014-03-07 9:08 ` Richard Biener
2014-03-10 18:29 ` Prathamesh Kulkarni
2014-03-11 11:20 ` Richard Biener
2014-03-13 11:14 ` Richard Biener
2014-03-14 15:31 ` Prathamesh Kulkarni
2014-03-14 15:35 ` Prathamesh Kulkarni
2014-03-14 15:55 ` Marc Glisse
2014-03-14 16:37 ` Prathamesh Kulkarni
2014-03-14 17:54 ` Marc Glisse
2014-03-14 17:16 ` Richard Biener
2014-03-16 12:21 ` Prathamesh Kulkarni
2014-03-17 8:52 ` Richard Biener [this message]
2014-03-18 8:13 ` Prathamesh Kulkarni
2014-03-19 0:27 ` Maxim Kuvyrkov
[not found] ` <CAJXstsD0Y=vBxw9QveOU3O3jhQgbYkxj_iyfje=AFypHEmK9gA@mail.gmail.com>
2014-03-19 9:43 ` Richard Biener
2014-03-20 20:52 ` Prathamesh Kulkarni
2014-03-21 9:49 ` 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='CAFiYyc2dwsfrS=69bNw0JGBeJY4krM--Q0FUMmkup2pVvJ2YMA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=bilbotheelffriend@gmail.com \
--cc=gcc@gcc.gnu.org \
/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).