public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lawrence Crowl <crowl@googlers.com>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Simplifying Gimple Generation
Date: Thu, 15 Nov 2012 19:34:00 -0000	[thread overview]
Message-ID: <CAGqM8fZO7ZNt9HzL7=ySTF=2ky368_jF6p1iZS4B1eR2UDE__A@mail.gmail.com> (raw)
In-Reply-To: <20121115060635.GA14640@ours.starynkevitch.net>

On 11/14/12, Basile Starynkevitch <basile@starynkevitch.net> wrote:
> On Wed, Nov 14, 2012 at 05:13:12PM -0800, Lawrence Crowl wrote:
>> Diego and I seek your comments on the following (loose) proposal.
>>
>>
>> Generating gimple and tree expressions require lots of detail,
>> which is hard to remember and easy to get wrong.  There is some
>> amount of boilerplate code that can, in most cases, be reduced and
>> managed automatically.
>>
>> We will add a set of helper classes to be used as local variables
>> to manage the details of handling the existing types.  That is,
>> a layer over 'gimple_build_*'. We intend to provide helpers for
>> those facilities that are both commonly used and have room for
>> significant simplification.
>
> I do agree (in principle) on this and the previous (debugging-like)
> proposal, but:
>
>   do you target the 4.8 release? (I believe not, since its stage 1 is
>   ending)

Not 4.8.

>   do you intend to remove the current way of doing?

Definitely not.  Our intent is to provide an easier tool that
accomplishes the common tasks.  We expect that tricky stuff will
use the existing interfaces.

-- 
Lawrence Crowl

  reply	other threads:[~2012-11-15 19:34 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 [this message]
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
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='CAGqM8fZO7ZNt9HzL7=ySTF=2ky368_jF6p1iZS4B1eR2UDE__A@mail.gmail.com' \
    --to=crowl@googlers.com \
    --cc=basile@starynkevitch.net \
    --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).