Hello,
> OK, with the following comments:
>
> Make sure reg_moves are generated for the correct (result, not addr)
> register, in generate_reg_moves().
>
> "been">>"being" (multiple appearances).
>
> Add a note that autoinc_var_is_used_p (rtx def_insn, rtx use_insn)
> doesn't need to consider the
Hello,
> Ok, this does have two anti-dep edges. But still, only a single true
> dependence(?) ... can you see why?
The intra edge [3681 -(T,2,0)-> 3682] was created by haifa-sched and I guess
that because both of the expected true-dep edges (one for the target
and one for the address) are identic
On Tue, Sep 27, 2011 at 9:47 AM, Revital Eres wrote:
> Hello,
>
>> ok, so if we have an auto-inc'ing insn which defines (auto-inc's) an
>> addr register and another (say, result) register, we want to allow the
>> result register to have life ranges in excess of ii (by eliminating
>> anti-dep edges
Hello,
> ok, so if we have an auto-inc'ing insn which defines (auto-inc's) an
> addr register and another (say, result) register, we want to allow the
> result register to have life ranges in excess of ii (by eliminating
> anti-dep edges of distance 1 from uses to def, and generating
> reg_moves i
On Mon, Sep 26, 2011 at 7:31 AM, Revital Eres wrote:
> Hello,
>
> This patch extends the implementation to support instructions with
> REG_INC notes.
> It addresses the comments from the previous submission:
> http://gcc.gnu.org/ml/gcc-patches/2011-08/msg01299.html.
>
ok, so if we have an auto-in
Hello,
This patch extends the implementation to support instructions with
REG_INC notes.
It addresses the comments from the previous submission:
http://gcc.gnu.org/ml/gcc-patches/2011-08/msg01299.html.
btw, regarding your previous question about the usage of the address
register been auto inc, ap
