From: Michael Matz <matz@suse.de>
To: Diego Novillo <dnovillo@google.com>
Cc: Lawrence Crowl <crowl@googlers.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Simplifying Gimple Generation
Date: Fri, 16 Nov 2012 14:30:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1211161529030.21868@wotan.suse.de> (raw)
In-Reply-To: <CAD_=9DSQ2AdOaEgpJpm7RAAR9EJSWemHRmq6khno6hF9mejE=g@mail.gmail.com>
Hi,
On Fri, 16 Nov 2012, Diego Novillo wrote:
> > I think consistency should trump brevity here, so also add a tree code for
> > the converter, i.e.
> > ssa_stmt b = q.stmt (NOP_EXPR, shadow_type, a);
>
> Ah, yes. This one was amusing. When we were drafting the proposal,
> Lawrence kept wondering what this NOP_EXPR thing is. I've been
> suffering this name for so long, that it no longer irritates me. Had
> it been named CAST_EXPR, or even NOP_CAST_EXPR, he would have probably
> kept it in the example code :)
We have CONVERT_EXPR, but it currently doesn't do _quite_ the same as
NOP_EXPR. I once wanted to merge them (with CONVERT_EXPR surviving), but
it stalled somewhere, couple years ago.
Ciao,
Michael.
next prev parent reply other threads:[~2012-11-16 14:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 1:13 Lawrence Crowl
2012-11-15 6:06 ` Basile Starynkevitch
2012-11-15 19:34 ` Lawrence Crowl
2012-11-16 13:15 ` Diego Novillo
2012-11-15 7:32 ` Xinliang David Li
2012-11-16 13:13 ` Diego Novillo
2012-11-17 1:05 ` Xinliang David Li
2012-11-15 14:48 ` Michael Matz
2012-11-15 16:52 ` Gabriel Dos Reis
2012-11-15 17:01 ` Michael Matz
2012-11-15 17:07 ` Xinliang David Li
2012-11-15 19:59 ` Lawrence Crowl
2012-11-16 12:44 ` Michael Matz
2012-11-16 13:59 ` Diego Novillo
2012-11-16 14:30 ` Michael Matz [this message]
2012-11-16 17:31 ` Andrew Pinski
2012-11-20 16:49 ` Andrew MacLeod
2012-11-25 1:35 ` Diego Novillo
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.LNX.2.00.1211161529030.21868@wotan.suse.de \
--to=matz@suse.de \
--cc=crowl@googlers.com \
--cc=dnovillo@google.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).