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: Deal with local static same way as we deal with global static for IPA

From: Richard Henderson <rth at redhat dot com>
To: Jan Hubicka <jh at suse dot cz>
Cc: gcc-patches at gcc dot gnu dot org, jason at redhat dot com, zadeck at naturalbridge dot com
Date: Wed, 8 Jun 2005 12:03:57 -0700
Subject: Re: Deal with local static same way as we deal with global static for IPA
References: <20050607201159.GW11634@kam.mff.cuni.cz> <20050608011126.GA24061@redhat.com> <20050608090251.GC11634@kam.mff.cuni.cz>

On Wed, Jun 08, 2005 at 11:02:51AM +0200, Jan Hubicka wrote:
> I don't see how to do that easilly - the BIND_EXPRs are linked via
> TREE_CHAIN pointers and we need the local static in two BIND_EXPRs at
> once, but we have only one link pointer.

I don't think it needs to be linked into the bind_expr at all.

We don't use the BIND_EXPRs for debugging, only the BLOCKs.  You may
need to insert the variable into the inliner's unexpanded_var_list,
to make sure that its DECL_RTL gets created at the right time, but
that should be about it.

r~

Follow-Ups:
- Re: Deal with local static same way as we deal with global static for IPA
  - From: Jan Hubicka

References:
- Deal with local static same way as we deal with global static for IPA
  - From: Jan Hubicka
- Re: Deal with local static same way as we deal with global static for IPA
  - From: Richard Henderson
- Re: Deal with local static same way as we deal with global static for IPA
  - From: Jan Hubicka

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