steakhal wrote:

This approach isn't correct. The problem is that the analyzer indeed exposes 
the host target endianness inside the `getStringRefAtRegion` function when it 
calls `Lit->getBytes()`. Those bytes are in host order.

Pinning targets isn't really helpful for solving this.

https://github.com/llvm/llvm-project/pull/213279
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to