Low level PhasePosition
s1255753 at sms.ed.ac.uk
Fri Jun 28 07:08:17 PDT 2013
I see. I tried replacing my phases with suites, but I wasn't able to get the same results out. Specifically, when I use suites instead of a phasePlan, it appears to me as if each "suite" receives a lower-level graph IR than the equivalent "phase". To illustrate, if I use a phasePlan, I get nodes like LoopBeginNode etc - with the equivalent suite, I don't. Perhaps I'm missing something though - I will investigate further.
On 24 Jun 2013, at 18:54, Mick Jordan <mick.jordan at oracle.com> wrote:
> On 6/24/13 10:47 AM, ATKIN-GRANVILLE Chris wrote:
>> Hi guys. Why was PhasePosition.LOW_LEVEL removed? I can't find any hints in the commit logs, nor any references to it in a current checkout of the repo. Is there a replacement for it?
> I don't know exactly why LOW_LEVEL was removed, but I do know that PhasePlan is in the process of being phased out (sic) to be replaced (eventually) by custom Suites.
> I used to use LOW_LEVEL and the way I worked around its demise was to use the appendPhase method on the PhaseSuite class, to add the phase to the end of the MidTier suite, e.g.
> bootSuites = Suites.createDefaultSuites();
> PhaseSuite<MidTierContext> midTier = bootSuites.getMidTier();
> midTier.appendPhase(new MyLowLevelPhase());
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
More information about the graal-dev