This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gfortran] Use MAX/MIN_EXPR to convert intrinsic min/max
- From: Canqun Yang <canqun at nudt dot edu dot cn>
- To: Steven Bosscher <stevenb at suse dot de>, gcc-patches at gcc dot gnu dot org,fortran at gcc dot gnu dot org
- Date: Sat, 31 Jan 2004 18:35:17 +0800 (HKT)
- Subject: Re: [gfortran] Use MAX/MIN_EXPR to convert intrinsic min/max
- References: <20040130022123.A6D2B5BDBD@ds20.nudt.edu.cn> <200401301030.24400.stevenb@suse.de>
- Reply-to: Canqun Yang <canqun at nudt dot edu dot cn>
ÒýÑÔ Steven Bosscher <stevenb@suse.de>:
> On Friday 30 January 2004 03:21, Canqun Yang wrote:
> > Hi, all
> >
> > Use MAX_EXPR or MIN_EXPR to convert the intrinsics
> > min/max and minval/maxval, compared with former
> > implementation which use if-then-else constructs,
seems
> > more straightforward, it will avoid the overhead for
> > GCC backend to do if-conversion.
>
> I think MIN_EXPR and MAX_EXPR are non-GIMPLE, so this
patch
> _should_ not make a difference on the generated
code. Have
> you checked that it does?
>
> Gr.
> Steven
>
>
Oh, you're right. MIN_EXPR and MAX_EXPR are non-GIMPLE.
gimplify.c will reduce MIN_EXPR and MAX_EXPR to
COND_EXPR.
Canqun Yang