Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of gcjhd-harmony-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@harmony.apache.org
From: George Timoshenko <george.timoshenko@gmail.com>
Subject: Re: [drlvm][opt] what does 'irBuilderFlags.expandMemAddrs' mean?
Date: Wed, 07 May 2008 09:46:15 +0700
Lines: 25
Message-ID: <482117F7.1080209@gmail.com>
References: <3db9f87f0805060621l10ca111ah807bbf066b23b29@mail.gmail.com>
 <0vqskwvjht0.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
In-Reply-To: <0vqskwvjht0.fsf@gmail.com>
Sender: news <news@ger.gmane.org>

expandMemAddr is true by default.
I am not sure if it wrorks correctly in the 'false' case.

This flag is obsolet actually.
It should be removed.

Egor Pasko wrote:
> On the 0x43C day of Apache Harmony Simon Chow wrote:
>> Hi all
>> I found this flag is frequently used when generating 'Store' related
>> instruction.
>> if it is set, makeMultiSrcInst is used, otherwise makeFieldAccessInst is
>> used, is that right? and Why is that?
> 
> after "Lazy Resolution" feature has been implemented, you can safely
> assume expandMemAddrs is always true, otherwise it just does not
> work.
> 
> true makes indirect loads by addresses
> false makes special instructions like ldfield
> 
> I dunno why there were two ways to do the same thing for ages. Maybe
> true value helped memopt (so you do not have to teach it with ldfield
> stuff), not sure.
>