Try the index function for finding the zero bytes in $s1.

(udpate: fixed typo)

Another update: now with complete code:

sub windex { my ($s1, $s2) = @_; my $pos = -1; my $null = chr 0; my $len = length $s1; while( ($pos = index $s1, $null, $pos+1) >= 0 ){ substr $s1, $pos, 1, substr($s2, $pos, 1); } return $s1; }

It's fast, but it won't win the beer:

Rate split1 substr1 index split1 4.32/s -- -84% -100% substr1 27.7/s 541% -- -99% index 3757/s 86900% 13478% --

But don't bother, I don't like beer.. ;-)

Another update: fixed initial value of $pos. See Re: Challenge: CPU-optimized byte-wise or-equals (for a meter of beer) and the follow ups for more details.


In reply to Re: Challenge: CPU-optimized byte-wise or-equals (for a meter of beer) by moritz
in thread Challenge: CPU-optimized byte-wise or-equals (for a meter of beer) by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.