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: [patch] Tidy up execute_update_addresses_taken

From: Eric Botcazou <ebotcazou at adacore dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Thu, 23 Sep 2010 08:28:29 +0200
Subject: Re: [patch] Tidy up execute_update_addresses_taken
References: <201009222335.18725.ebotcazou@adacore.com> <AANLkTimm=PDU4wuAk_gdH-vU+1ZWGHdGqjK5jyUiiV8i@mail.gmail.com>

> Huh, interesting ;)  I wonder when we dropped the last caller with
> false or !optimize ...

You (re-)introduced one yesterday. :-)  So the patch must be adjusted.  What 
about calling execute_update_addresses_taken from execute_function_todo only 
if OPTIMIZE is true?  That would avoid running the collecting phase for 
nothing.  Or else early returning from the function if !OPTIMIZE?

-- 
Eric Botcazou

Follow-Ups:
- Re: [patch] Tidy up execute_update_addresses_taken
  - From: Richard Guenther

References:
- [patch] Tidy up execute_update_addresses_taken
  - From: Eric Botcazou
- Re: [patch] Tidy up execute_update_addresses_taken
  - From: Richard Guenther

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