This is the mail archive of the gcc@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: IRA for GCC 4.4

From: Paolo Bonzini <bonzini at gnu dot org>
To: Vladimir Makarov <vmakarov at redhat dot com>
Cc: FX <fxcoudert at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>, Steven Bosscher <stevenb dot gcc at gmail dot com>
Date: Thu, 24 Apr 2008 16:51:55 +0200
Subject: Re: IRA for GCC 4.4
References: <19c433eb0804240214r7bec8115p47d93a97ea40e8e8@mail.gmail.com> <481090E0.9000004@redhat.com> <19c433eb0804240728y47cedebeofdfde1629fe64aa5@mail.gmail.com> <48109C69.8000704@redhat.com>

(The testcase is 400k lines of preprocessed Fortran code, 16M is size,
available here:
http://www.pci.unizh.ch/vandevondele/tmp/all_cp2k_gfortran.f90.gz)

Thanks, I'll check it.

Vlad, I think you should also try to understand what does trunk do with global (and without local allocation) at -O0. That will give a measure of the benefit from Peter's patches for conflict graph building.

Another thing to evaluate is the impact of changing gimplify.c so that it always follows the "if (optimize)" paths. The differences are there exactly because we don't run global register allocation at -O0, and they create more pseudos.

Paolo

Follow-Ups:
- Re: IRA for GCC 4.4
  - From: Peter Bergner

References:
- Re: IRA for GCC 4.4
  - From: FX
- Re: IRA for GCC 4.4
  - From: Vladimir Makarov
- Re: IRA for GCC 4.4
  - From: FX
- Re: IRA for GCC 4.4
  - From: Vladimir Makarov

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