This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: in search of clue regarding -fcheck-memory-usage
- To: zackw at stanford dot edu
- Subject: Re: in search of clue regarding -fcheck-memory-usage
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Sun, 21 Jan 2001 12:38:32 -0800
- Cc: gcc at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <20010120220828.B297@wolery.stanford.edu>
>>>>> "Zack" == Zack Weinberg <zackw@stanford.edu> writes:
Zack> My major concern is that up till now 'reg' had been
Zack> destructively replaced by a MEM rtx before we got here. My
Zack> changes are going to postpone that until after we're done
Zack> generating RTL. So XEXP (reg, 0) is now an invalid
Zack> operation. What should I be replacing it with?
An ADDRESSOF? Isn't what the thing wants in the end -- the address of
some memory? So, you can use ADDRESSOF (REG), and then rely on the
ADDRESSOF pass to insert this stuff later.
This is part of why I objected to the design of the -fcheck-memory
stuff; it is too interleaved with ordinary compiler processing. It
should be a separate pass -- either on trees or RTL.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com