This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Don't lower MIN_EXPR and MAX_EXPR [was Re: GCC Benchmarks (coybench), AMD64 and i686, 14 August 2004]
- From: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
- To: Paolo Bonzini <bonzini at gnu dot org>, gcc-patches at gcc dot gnu dot org
- Cc: Daniel Berlin <dberlin at dberlin dot org>,"gcc at gcc dot gnu dot org list" <gcc at gcc dot gnu dot org>
- Date: Thu, 19 Aug 2004 09:46:16 +0200
- Subject: Re: [PATCH] Don't lower MIN_EXPR and MAX_EXPR [was Re: GCC Benchmarks (coybench), AMD64 and i686, 14 August 2004]
- References: <41232983.5040709@kss-loka.si> <DFCE108B-F115-11D8-AC31-000A95DA505C@dberlin.org> <41244DA0.6000504@gnu.org>
On Thursday 19 August 2004 08:50, Paolo Bonzini wrote:
> > I thought we had this discussion a while ago, and the result was "MIN
> > and MAX are GIMPLE, but we might as well keep the early simplification"
> > for some reason.
>
> Here is a patch to disable it. I don't see any benefit in it.
IIRC the benefit of lowering is that it may allow you to propagate
the condition and the assignment if you lower the {MIN,MAX}_EXPR.
Have you looked at how your patch affects DOM and GVN-PRE?
Gr.
Steven