2011/5/28 Georg-Johann Lay :
> Georg-Johann Lay wrote:
>>
>> Georg-Johann Lay wrote:
>>
>>> Richard Henderson wrote:
>>>
>>>
Why are you adding "optimize" to all these insns? None of them will
be matched unless combine is run, which implies optimization.
>>>
>>> Here is a patch without o
Georg-Johann Lay wrote:
Georg-Johann Lay wrote:
Richard Henderson wrote:
Why are you adding "optimize" to all these insns? None of them will
be matched unless combine is run, which implies optimization.
Here is a patch without optimize in the insn conditions.
The optimize condition is st
Georg-Johann Lay schrieb:
> Richard Henderson schrieb:
>
>> Why are you adding "optimize" to all these insns? None of them will
>> be matched unless combine is run, which implies optimization.
>
> Here is a patch without optimize in the insn conditions.
>
> The optimize condition is still prese
Georg-Johann Lay schrieb:
> Richard Henderson schrieb:
>
>> Why are you adding "optimize" to all these insns? None of them will
>> be matched unless combine is run, which implies optimization.
>
> Here is a patch without optimize in the insn conditions.
>
> The optimize condition is still prese
Richard Henderson schrieb:
> Why are you adding "optimize" to all these insns? None of them will
> be matched unless combine is run, which implies optimization.
Here is a patch without optimize in the insn conditions.
The optimize condition is still present in the insv expander because I
do not
Richard Henderson schrieb:
> On 04/26/2011 04:51 AM, Georg-Johann Lay wrote:
>> As the SFRs are volatile, insv expander skips
>> them and a combine pattern must care of them. Omitting the complicated
>> bit-plethora patterns I still see long, slow shift loops for HI. So
>> the patch still includes
On 04/26/2011 04:51 AM, Georg-Johann Lay wrote:
> As the SFRs are volatile, insv expander skips
> them and a combine pattern must care of them. Omitting the complicated
> bit-plethora patterns I still see long, slow shift loops for HI. So
> the patch still includes them.
Why don't we focus on doin
Richard Henderson schrieb:
> On 04/21/2011 05:31 AM, Georg-Johann Lay wrote:
>> +;; Some combiner patterns dealing with bits.
>> +;; See PR42210
>> +
>> +;; Move bit $3.$4 into bit $0.$4
>> +(define_insn "*movbitqi.1-6.a"
> ...
>> +(define_insn "*movbitqi.1-6.b"
> ...
>> +(define_insn "*movbitqi.0"
On 04/21/2011 05:31 AM, Georg-Johann Lay wrote:
> +;; Some combiner patterns dealing with bits.
> +;; See PR42210
> +
> +;; Move bit $3.$4 into bit $0.$4
> +(define_insn "*movbitqi.1-6.a"
...
> +(define_insn "*movbitqi.1-6.b"
...
> +(define_insn "*movbitqi.0"
...
> +(define_insn "*movbitqi.7"
This
Georg-Johann Lay schrieb:
> This solves some missed optimization that can be seen when moving
> around bits.
>
> There are 4 combiner patterns that operate on regs and one that uses
> them as intermediate patterns and works on I/O. Even if just an
> intermediate pattern matches it's still an impro
This solves some missed optimization that can be seen when moving
around bits.
There are 4 combiner patterns that operate on regs and one that uses
them as intermediate patterns and works on I/O. Even if just an
intermediate pattern matches it's still an improvement because avoid
of shift.
Tested
11 matches
Mail list logo