Displaying 6 results from an estimated 6 matches for "performselectcombine".
2013 Aug 19
2
[LLVMdev] [X86] DAG Combine - VSELECT
Hi @ll,
I am wondering about the use of !isBeforeLegalize in PerformSELECTCombine in the X86 backend. This defers all VSELECT related DAG combines until after the Legalizer has run. If the IR has already only legal types the second round of DAG combines is skipped and no VSELECT specified optimizations are performed at all.
Is there a reason we don’t run the X86 DAG combiner be...
2013 Aug 19
3
[LLVMdev] [X86] DAG Combine - VSELECT
...e check before type legalization to enable it?
On Aug 19, 2013, at 4:13 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
> On Mon, Aug 19, 2013 at 3:34 PM, Juergen Ributzka <juergen at apple.com> wrote:
> Hi @ll,
>
> I am wondering about the use of !isBeforeLegalize in PerformSELECTCombine in the X86 backend. This defers all VSELECT related DAG combines until after the Legalizer has run. If the IR has already only legal types the second round of DAG combines is skipped and no VSELECT specified optimizations are performed at all.
>
> Is there a reason we don’t run the X86 DAG c...
2013 Aug 20
0
[LLVMdev] [X86] DAG Combine - VSELECT
...Legalize check.
-Eli
> On Aug 19, 2013, at 4:13 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
>
> On Mon, Aug 19, 2013 at 3:34 PM, Juergen Ributzka <juergen at apple.com>wrote:
>
>> Hi @ll,
>>
>> I am wondering about the use of !isBeforeLegalize in PerformSELECTCombine
>> in the X86 backend. This defers all VSELECT related DAG combines until
>> after the Legalizer has run. If the IR has already only legal types the
>> second round of DAG combines is skipped and no VSELECT specified
>> optimizations are performed at all.
>>
>> I...
2013 Aug 19
0
[LLVMdev] [X86] DAG Combine - VSELECT
On Mon, Aug 19, 2013 at 3:34 PM, Juergen Ributzka <juergen at apple.com> wrote:
> Hi @ll,
>
> I am wondering about the use of !isBeforeLegalize in PerformSELECTCombine
> in the X86 backend. This defers all VSELECT related DAG combines until
> after the Legalizer has run. If the IR has already only legal types the
> second round of DAG combines is skipped and no VSELECT specified
> optimizations are performed at all.
>
> Is there a reason we don’...
2013 Aug 20
1
[LLVMdev] [X86] DAG Combine - VSELECT
...9, 2013, at 4:13 PM, Eli Friedman <eli.friedman at gmail.com<mailto:eli.friedman at gmail.com>> wrote:
On Mon, Aug 19, 2013 at 3:34 PM, Juergen Ributzka <juergen at apple.com<mailto:juergen at apple.com>> wrote:
Hi @ll,
I am wondering about the use of !isBeforeLegalize in PerformSELECTCombine in the X86 backend. This defers all VSELECT related DAG combines until after the Legalizer has run. If the IR has already only legal types the second round of DAG combines is skipped and no VSELECT specified optimizations are performed at all.
Is there a reason we don't run the X86 DAG combine...
2007 Aug 08
2
[LLVMdev] Destination register needs to be valid after callee saved register restore when tail calling
Hello, Arnold.
> with the sentence i tried to express the question whether there is a
> way to persuade the code generator to use another register to load (or
> move) the function pointer to (right before the callee saved register
> restore) but thinking a little further that's nonsense.
Why don't define some special op for callee address and custom lower it?
I really