This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [tuples] C++: gimplify TRY_BLOCK and HANDLER, and EH_SPEC_BLOCK
- From: "Diego Novillo" <dnovillo at google dot com>
- To: "Aldy Hernandez" <aldyh at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, jason at redhat dot com
- Date: Thu, 18 Oct 2007 12:57:56 -0400
- Subject: Re: [tuples] C++: gimplify TRY_BLOCK and HANDLER, and EH_SPEC_BLOCK
- References: <20071018165311.GA5247@redhat.com>
On 10/18/07, Aldy Hernandez <aldyh@redhat.com> wrote:
> What is the recommended approach... should we gimplify entirely in the
> C++ side, if possible and trivial, or should we convert to GENERIC and
> let the gimplifier work? I don't want to start a bad precedent if the
> initial design was to keep things in GENERIC and pass it off, but cherry
> picking these easy cases seem like a good way to go.
My inclination is to have the C++ FE emit GENERIC instead of
microoptimizing into GIMPLE directly. It gives us a lot more
flexibility and separation.
However, if we take a severe performance hit because of that, then we
should probably go to GIMPLE directly. I kind of doubt that will be
the case, but we should experiment when testing the branch.