On Mon, May 7, 2012 at 10:20 PM, Vladimir Makarov wrote:
> On 04/26/2012 04:49 AM, Bin.Cheng wrote:
>>
>> On Wed, Apr 25, 2012 at 10:46 PM, Vladimir Makarov
>> wrote:
>>>
>>> On 04/24/2012 11:56 PM, Bin.Cheng wrote:
Hi,
In scan_one_insn, gcc checks whether an insn loads a parameter
On 04/26/2012 04:49 AM, Bin.Cheng wrote:
On Wed, Apr 25, 2012 at 10:46 PM, Vladimir Makarov wrote:
On 04/24/2012 11:56 PM, Bin.Cheng wrote:
Hi,
In scan_one_insn, gcc checks whether an insn loads a parameter from
its stack slot, and then
record the fact by decrease the memory cost.
What I do n
On Wed, Apr 25, 2012 at 10:46 PM, Vladimir Makarov wrote:
> On 04/24/2012 11:56 PM, Bin.Cheng wrote:
>>
>> Hi,
>> In scan_one_insn, gcc checks whether an insn loads a parameter from
>> its stack slot, and then
>> record the fact by decrease the memory cost.
>>
>> What I do not understand is the ch
On 04/24/2012 11:56 PM, Bin.Cheng wrote:
Hi,
In scan_one_insn, gcc checks whether an insn loads a parameter from
its stack slot, and then
record the fact by decrease the memory cost.
What I do not understand is the check condition like below checks the
REG_EQUIV note, rather than
checking memory
Hi,
In scan_one_insn, gcc checks whether an insn loads a parameter from
its stack slot, and then
record the fact by decrease the memory cost.
What I do not understand is the check condition like below checks the
REG_EQUIV note, rather than
checking memory access using stack pointer directly.
if