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: reg_equiv_memory_loc vs. garbage collection

From: Jim Wilson <wilson at specifixinc dot com>
To: Joern Rennecke <joern dot rennecke at superh dot com>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 13 May 2004 23:38:27 -0700
Subject: Re: reg_equiv_memory_loc vs. garbage collection
References: <200405061502.i46F26519203@linsvr5.uk.superh.com>

Joern Rennecke wrote:

It appears that rtl referenced by reg_equiv_memory_loc lives across
a garbage collection point.

This is an SH specific problem, as the SH port is the only one that defines the ALLOCATE_INITIAL_VALUE macro. The definition in config/sh/sh.h has no comment, so I don't know what it is doing. It also turns out that this is code you wrote. So you probably should try to fix it yourself.

You might also consider whether having SH specific macros in the optimizer is a good idea. The cost of maintaining them may not be worth the trouble.

Note that reporting a bug to the gcc list doesn't really do anything useful. If you want the SH port fixed, and you don't plan to fix it yourself, then you should create a bugzilla bug report. Otherwise, it will just be forgotten. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Follow-Ups:
- Re: reg_equiv_memory_loc vs. garbage collection
  - From: Joern Rennecke
- RFA: make reg_equiv_memory_loc visible to garbage collector (Was: Re: reg_equiv_memory_loc vs. garbage collection)
  - From: Joern Rennecke

References:
- reg_equiv_memory_loc vs. garbage collection
  - From: Joern Rennecke

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