On Thu, 29 Jan 2015, Clint Byrum wrote: > Fair enough?
In some cases, the patch to fix the behaviour for some architectures may-or-may-not-(but-this-has-to-be-proven) hurt performance or something on other architectures while retaining correctness. In these cases, always if the language does not have #ifdef, but even sometimes if it does, it’s better to use the one correct, slower on some architectures, codepath than to over-optimise – for example, see the recent discussion here about unaligned data access on various architectures, where it was even‐ tually agreed to use the “safe” codepath everywhere, to avoid UB and other pitfalls. bye, //mirabilos -- 15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.11.1502031533420.21...@tglase.lan.tarent.de
