This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Combine four insns

From: Jeff Law <law at redhat dot com>
To: Steven Bosscher <stevenb dot gcc at gmail dot com>
Cc: Paolo Bonzini <bonzini at gnu dot org>, Bernd Schmidt <bernds at codesourcery dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 06 Aug 2010 12:02:15 -0600
Subject: Re: Combine four insns
References: <4C5C20D0.5020105@codesourcery.com> <AANLkTim2HTajArcbffK=gRX=tshhc+nhU2GXgQU-O5mz@mail.gmail.com> <4C5C3C23.2040706@gnu.org> <AANLkTimt3eS1+GBvCmsUTOxQUiKF2toOB3w8eVvLjT7B@mail.gmail.com>

On 08/06/10 11:22, Steven Bosscher wrote:

On Fri, Aug 6, 2010 at 6:45 PM, Paolo Bonzini<bonzini@gnu.org> wrote:
But perhaps the optimization can be performed in another place than
combine? If it's just a relatively small set of common patterns, a
quick GIMPLE pass may be preferable.
I think this part of my message was much more interesting to respond to.

This code naturally belongs in combine, putting it anywhere else is just, umm, silly.

jeff

Follow-Ups:
- Re: Combine four insns
  - From: Steven Bosscher

References:
- Combine four insns
  - From: Bernd Schmidt
- Re: Combine four insns
  - From: Steven Bosscher
- Re: Combine four insns
  - From: Paolo Bonzini
- Re: Combine four insns
  - From: Steven Bosscher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]