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 ping (IA-64, C++, Debug)

From: Richard Henderson <rth at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Jason Merrill <jason at redhat dot com>, Cary Coutant <ccoutant at google dot com>, gcc-patches at gcc dot gnu dot org, Roland McGrath <roland at redhat dot com>
Date: Mon, 06 Dec 2010 11:08:50 -0800
Subject: Re: Patch ping (IA-64, C++, Debug)
References: <20101206121238.GR29412@tyan-ft48-01.lab.bos.redhat.com> <4CFD28C1.8000900@redhat.com> <20101206190636.GW29412@tyan-ft48-01.lab.bos.redhat.com>

On 12/06/2010 11:06 AM, Jakub Jelinek wrote:
>> Ok in principal.  Was there a specific reason to change ENTRY_VALUE's
>> argument from "e" to "0"?  At first glance like it just expands the
>> amount of support code needed for no reason...
> 
> The reason was to make most of the rtl optimizations etc. treat the
> ENTRY_VALUE as a black box.  If it is not treated as a black box,
> then e.g. DF treats it as uses of the corresponding parameter register
> (when it actually is not anything like that).

That's the answer I was looking for.

Patch is ok as-is.


r~

References:
- Patch ping (IA-64, C++, Debug)
  - From: Jakub Jelinek
- Re: Patch ping (IA-64, C++, Debug)
  - From: Richard Henderson
- Re: Patch ping (IA-64, C++, Debug)
  - From: Jakub Jelinek

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