Displaying 7 results from an estimated 7 matches for "findcandidates".
2017 Sep 28
3
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...>> MachineOutliner, the method by which we do this is decided on by the target.
>>
>> So, we at the very least might want an interface that implements something
>> like
>>
>> unsigned mapInstructions(…);
>> unsigned getOutliningCost(…);
>> unsigned findCandidates(…);
>> bool outline(…);
>>
>
> Hi Jessica, I tend to agree we should try to maximize code reuse in
> this context, and I think yours is a good step forward. In particular,
> I'm particularly confident the `findCandidates()` bits should be
> split.
> That said, do...
2017 Sep 27
0
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...o a newly-created function. In the
> MachineOutliner, the method by which we do this is decided on by the target.
>
> So, we at the very least might want an interface that implements something
> like
>
> unsigned mapInstructions(…);
> unsigned getOutliningCost(…);
> unsigned findCandidates(…);
> bool outline(…);
>
Hi Jessica, I tend to agree we should try to maximize code reuse in
this context, and I think yours is a good step forward. In particular,
I'm particularly confident the `findCandidates()` bits should be
split.
That said, do we really want encapsulate the logic f...
2017 Sep 28
0
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...o a newly-created function. In the
> MachineOutliner, the method by which we do this is decided on by the target.
>
> So, we at the very least might want an interface that implements something
> like
>
> unsigned mapInstructions(…);
> unsigned getOutliningCost(…);
> unsigned findCandidates(…);
> bool outline(…);
>
>
> Hi Jessica, I tend to agree we should try to maximize code reuse in
> this context, and I think yours is a good step forward. In particular,
> I'm particularly confident the `findCandidates()` bits should be
> split.
> That said, do we really...
2017 Sep 27
1
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...>> MachineOutliner, the method by which we do this is decided on by the target.
>>
>> So, we at the very least might want an interface that implements something
>> like
>>
>> unsigned mapInstructions(…);
>> unsigned getOutliningCost(…);
>> unsigned findCandidates(…);
>> bool outline(…);
>>
>
> Hi Jessica, I tend to agree we should try to maximize code reuse in
> this context, and I think yours is a good step forward. In particular,
> I'm particularly confident the `findCandidates()` bits should be
> split.
> That said, do...
2017 Sep 27
3
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...sequence of instructions with a call to a newly-created function. In the MachineOutliner, the method by which we do this is decided on by the target.
So, we at the very least might want an interface that implements something like
unsigned mapInstructions(…);
unsigned getOutliningCost(…);
unsigned findCandidates(…);
bool outline(…);
The MachineOutliner is *almost* set up like this. So, I think it should be pretty easy to build the split this way without a lot of adaptation. The only place I can see it being somewhat tricky is maybe with all of the target-specified information in the MachineOutliner. I thi...
2017 Sep 27
0
[RFC] PT.2 Add IR level interprocedural outliner for code size.
> On Sep 21, 2017, at 8:02 PM, River Riddle <riddleriver at gmail.com> wrote:
>
> Hey Gerolf,
>
> On Thu, Sep 21, 2017 at 7:10 PM, Gerolf Hoflehner <ghoflehner at apple.com <mailto:ghoflehner at apple.com>> wrote:
> In general I would love to see an outliner at the IR level also. But rather than a comparison vs. the machine outliner I would like to learn more
2017 Sep 22
2
[RFC] PT.2 Add IR level interprocedural outliner for code size.
Hey Gerolf,
On Thu, Sep 21, 2017 at 7:10 PM, Gerolf Hoflehner <ghoflehner at apple.com>
wrote:
> In general I would love to see an outliner at the IR level also. But
> rather than a comparison vs. the machine outliner I would like to learn
> more about how the core data structures between the outliners will be
> shared.
>
The only structure that needs to be shared is a