<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/128737>128737</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            [libc++] Benchmark non-trivial types for the copy/move family of algorithms
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            libc++
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
            ldionne
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          ldionne
      </td>
    </tr>
</table>

<pre>
    > For the copy family of algorithms I think it would be interesting to test some non-trivial type. Specifically, that the compiler would not be able to see through the operation. That could be achieved by an out-of-line definition or a `[[gnu::noinline]]` on the function. Maybe just an optimization barrier would work to.

_Originally posted by @philnik777 in https://github.com/llvm/llvm-project/pull/127354#discussion_r1968301004_
 
</pre>
<img width="1" height="1" alt="" src="http://email.email.llvm.org/o/eJyUkkGPm0AMhX_NcLESDQOE5MBh0zRSD1UP7X01gAFvhjGaMVnRX19BdtuV2kslC6SR_fye9dkYqfeIlSrOyhjXEnuPyhhVXBI7y8ChentMam6XSmWf4coBZEBoeFqgsyO5BbgD63oOJMMY4QvIQP4GJPDKs2uhRiAvGDAK-R6EQTAKRB4RPPudBLqTdSDLhHv4PmFDHTXWuUWZTyCDlbeN40QOw5uqZ1mVbe1wlYyIIEPguR-2bp4wWCH2e_ixKjTvVmwzEN6xhXoB64Fn2XG3c-QRWuzI0zoEHMCCOuj1NMW597PKnlT25Jn82qqKy1oHDey3dd3sm8e2r3apEV7mKJv8JDTSz80J1DYE-h3glcMNhPdKX5R-enyfvwXqya_ZYeIoD5sq19NAztOtLEsgD4PIFFdH5qrMtScZ5nrf8KjM1bn7-283BX7BRpS5TrNzylxTU2ZFrkzWUmzmGIn9c0hPh2OmU63z54cJSNoqa0_ZySZYpWWuC61PJk-GSjfp0XRZ3ZUHnWd5V2ZZcSrtITW1zcuTSagy2hTamCI9mGOe74u2axpTZHVr0_yYlyrXOFpy-9XgnkOfUIwzVqk5llmZOFuji-9AUt0oc95qYzJUW6x67qPKtaMo8Y-OkLgN5Q9jxQXO6JthtOH2F2oRug8sK3Md-Y7_RDqZg6v---ZbsLhdfct2r8yvAAAA___a-iLJ">