Displaying 4 results from an estimated 4 matches for "lbb2_32".
2018 Feb 22
2
Sink redundant spill after RA
...s successors, and there is no reload in other paths through
other successors. Since the spill is reloaded only in a certain path, it
must be okay to sink such spill close to its reloads. In the AArch64 code
below, there is a spill(x2) in the entry, but this value is reloaded only
in %bb.1, not in .LBB2_32. If we sink the spill (str x2, [sp, #120]) from
the entry to its successor (%bb.1), the load-from-store promotion might
catch this and replace the ldr in %bb.1 with a mov instruction. As we move
such spill down to its successor, we can also encourage more shrink-wrapping
as well.
.globl _mytes...
2018 Feb 22
2
Sink redundant spill after RA
...ere is no reload in
> other paths through other successors. Since the spill is reloaded only
> in a certain path, it must be okay to sink such spill close to its
> reloads. In the AArch64 code below, there is a spill(x2) in the entry,
> but this value is reloaded only in %bb.1, not in .LBB2_32. If we sink
> the spill (str x2, [sp, #120]) from the entry to its successor
> (%bb.1), the load-from-store promotion might catch this and replace
> the ldr in %bb.1 with a mov instruction. As we move such spill down to
> its successor, we can also encourage more shrink-wrapping as well...
2018 Feb 22
0
Sink redundant spill after RA
...s successors, and there is no reload in other paths through
other successors. Since the spill is reloaded only in a certain path, it
must be okay to sink such spill close to its reloads. In the AArch64 code
below, there is a spill(x2) in the entry, but this value is reloaded only
in %bb.1, not in .LBB2_32. If we sink the spill (str x2, [sp, #120]) from
the entry to its successor (%bb.1), the load-from-store promotion might
catch this and replace the ldr in %bb.1 with a mov instruction. As we move
such spill down to its successor, we can also encourage more shrink-wrapping
as well.
.globl _mytes...
2018 Feb 22
0
Sink redundant spill after RA
...> > other paths through other successors. Since the spill is reloaded only
> > in a certain path, it must be okay to sink such spill close to its
> > reloads. In the AArch64 code below, there is a spill(x2) in the entry,
> > but this value is reloaded only in %bb.1, not in .LBB2_32. If we sink
> > the spill (str x2, [sp, #120]) from the entry to its successor
> > (%bb.1), the load-from-store promotion might catch this and replace
> > the ldr in %bb.1 with a mov instruction. As we move such spill down to
> > its successor, we can also encourage more shr...