[Bug target/115065] AVR clz is not always fast as can be

2024-05-18 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115065 Georg-Johann Lay changed: What|Removed |Added Priority|P3 |P5 Severity|normal

[Bug target/115065] AVR clz is not always fast as can be

2024-05-18 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115065 --- Comment #3 from GCC Commits --- The releases/gcc-14 branch has been updated by Georg-Johann Lay : https://gcc.gnu.org/g:3b88dade7ff8a07fd0843ac1281e095cfd94453e commit r14-10217-g3b88dade7ff8a07fd0843ac1281e095cfd94453e Author: Wolfgang Ho

[Bug target/115065] AVR clz is not always fast as can be

2024-05-18 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115065 --- Comment #2 from GCC Commits --- The master branch has been updated by Georg-Johann Lay : https://gcc.gnu.org/g:988838da722dea09bd81ee9d49800a6f24980372 commit r15-645-g988838da722dea09bd81ee9d49800a6f24980372 Author: Wolfgang Hospital Dat

[Bug target/115065] AVR clz is not always fast as can be

2024-05-18 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115065 --- Comment #1 from Georg-Johann Lay --- IIUC, this is just about the timing of a branch, which in the general != 0 is currently taken (takes 2 ticks), but it's better to only take it in the non-common (= 0) case? So that the common case falls t