[Bug tree-optimization/110589] New: Missed optimization with call-clobbered restrict qualified references

2023-07-07 Thread javier.martinez.bugzilla at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110589 Bug ID: 110589 Summary: Missed optimization with call-clobbered restrict qualified references Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug rtl-optimization/71923] return instruction emitted twice with branch target inbetween

2023-07-18 Thread javier.martinez.bugzilla at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71923 Javier Martinez changed: What|Removed |Added CC||javier.martinez.bugzilla@gm

[Bug rtl-optimization/110724] New: Unnecessary alignment on branch to unconditional branch targets

2023-07-18 Thread javier.martinez.bugzilla at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110724 Bug ID: 110724 Summary: Unnecessary alignment on branch to unconditional branch targets Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/110724] Unnecessary alignment on branch to unconditional branch targets

2023-07-18 Thread javier.martinez.bugzilla at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110724 --- Comment #3 from Javier Martinez --- The generic tuning of 16:11:8 looks reasonable to me, I do not argue against it. 

From Anger Fog’s Optimizing subroutines in assembly language: 
> Most microprocessors fetch code in aligned 16-byte or 3

[Bug target/110724] Unnecessary alignment on branch to unconditional branch targets

2023-07-19 Thread javier.martinez.bugzilla at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110724 --- Comment #7 from Javier Martinez --- Another case where it might be interesting to remove padding (or reduce the :m threshold) is when the path is known to be cold. I can see Trunk padding labels inside [clone .cold], and with attribute((col