On 28 October 2013 11:31, Matt Turner matts...@gmail.com 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/
On 28 October 2013 11:31, Matt Turner matts...@gmail.com 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
On Wed, Oct 30, 2013 at 9:30 AM, Paul Berry stereotype...@gmail.com wrote:
On 28 October 2013 11:31, Matt Turner matts...@gmail.com 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
On Wed, Oct 30, 2013 at 10:06 AM, Paul Berry stereotype...@gmail.com wrote:
On 28 October 2013 11:31, Matt Turner matts...@gmail.com 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
On 30 October 2013 10:10, Matt Turner matts...@gmail.com wrote:
On Wed, Oct 30, 2013 at 9:30 AM, Paul Berry stereotype...@gmail.com
wrote:
On 28 October 2013 11:31, Matt Turner matts...@gmail.com wrote:
fs_visitor::try_replace_with_sel optimizes only if statements whose
then and else
On 30 October 2013 10:23, Paul Berry stereotype...@gmail.com wrote:
On 30 October 2013 10:10, Matt Turner matts...@gmail.com wrote:
On Wed, Oct 30, 2013 at 9:30 AM, Paul Berry stereotype...@gmail.com
wrote:
On 28 October 2013 11:31, Matt Turner matts...@gmail.com 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 arguments, since they cause an extra MOV
immediate to be generated