On 30 October 2013 10:23, Paul Berry wrote:
> On 30 October 2013 10:10, Matt Turner wrote:
>
>> On Wed, Oct 30, 2013 at 9:30 AM, Paul Berry
>> wrote:
>> > On 28 October 2013 11:31, Matt Turner wrote:
>> >>
>> >> fs_visitor::try_replace_with_sel optimizes only if statements whose
>> >> "then" a
On 30 October 2013 10:10, Matt Turner wrote:
> On Wed, Oct 30, 2013 at 9:30 AM, Paul Berry
> wrote:
> > On 28 October 2013 11:31, Matt Turner wrote:
> >>
> >> fs_visitor::try_replace_with_sel optimizes only if statements whose
> >> "then" and "else" bodies contain a single MOV instruction. It a
On Wed, Oct 30, 2013 at 10:06 AM, Paul Berry wrote:
> On 28 October 2013 11:31, Matt Turner wrote:
>>
>> fs_visitor::try_replace_with_sel optimizes only if statements whose
>> "then" and "else" bodies contain a single MOV instruction. It also did
>> could not handle constant arguments, since they
On Wed, Oct 30, 2013 at 9:30 AM, Paul Berry wrote:
> On 28 October 2013 11:31, Matt Turner wrote:
>>
>> fs_visitor::try_replace_with_sel optimizes only if statements whose
>> "then" and "else" bodies contain a single MOV instruction. It also did
>> could not handle constant arguments, since they
On 28 October 2013 11:31, Matt Turner wrote:
> fs_visitor::try_replace_with_sel optimizes only if statements whose
> "then" and "else" bodies contain a single MOV instruction. It also did
> could not handle constant arguments, since they cause an extra MOV
> immediate to be generated (since we ha
On 28 October 2013 11:31, Matt Turner wrote:
> fs_visitor::try_replace_with_sel optimizes only if statements whose
> "then" and "else" bodies contain a single MOV instruction. It also did
> could not handle constant arguments, since they cause an extra MOV
>
s/did could not/could not/
> immedi
On Tue, Oct 29, 2013 at 4:57 AM, Pohjolainen, Topi
wrote:
> On Mon, Oct 28, 2013 at 11:31:33AM -0700, Matt Turner wrote:
>> fs_visitor::try_replace_with_sel optimizes only if statements whose
>> "then" and "else" bodies contain a single MOV instruction. It also did
>> could not handle constant arg
On Mon, Oct 28, 2013 at 11:31:33AM -0700, Matt Turner wrote:
> fs_visitor::try_replace_with_sel optimizes only if statements whose
> "then" and "else" bodies contain a single MOV instruction. It also did
> could not handle constant arguments, since they cause an extra MOV
> immediate to be generate
fs_visitor::try_replace_with_sel optimizes only if statements whose
"then" and "else" bodies contain a single MOV instruction. It also did
could not handle constant arguments, since they cause an extra MOV
immediate to be generated (since we haven't run constant propagation,
there are more than the
