[Bug tree-optimization/119294] New: Strange (buggy?) codegen when passing cleared vector as argument

2025-03-14 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119294 Bug ID: 119294 Summary: Strange (buggy?) codegen when passing cleared vector as argument Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/119103] shift not demotated when shift amount range is known

2025-03-05 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119103 --- Comment #16 from Niklas Haas --- (In reply to Alexander Monakov from comment #15) > (In reply to Niklas Haas from comment #12) > > Out of curiosity, is there a work-around that I could use to get current > > versions of GCC to compile the ri

[Bug tree-optimization/119103] shift not demotated when shift amount range is known

2025-03-04 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119103 --- Comment #12 from Niklas Haas --- Out of curiosity, is there a work-around that I could use to get current versions of GCC to compile the right thing, but without breaking cross-platform compatibility? I did try replacing the assertion by "x

[Bug tree-optimization/119103] Very suboptimal AVX2 code generation of simple shift loop

2025-03-03 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119103 --- Comment #1 from Niklas Haas --- Clang's output for comparison: lshift: vmovdqu ymm0, ymmword ptr [rdi] vmovd xmm1, esi vpsllw ymm0, ymm0, xmm1 vmovdqu ymmword ptr [rdi], ymm0 vzeroupper ret

[Bug tree-optimization/119103] New: Very suboptimal AVX2 code generation of simple shift loop

2025-03-03 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119103 Bug ID: 119103 Summary: Very suboptimal AVX2 code generation of simple shift loop Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Pri

[Bug c/103738] No warning when setting deprecated fields using designated initializers

2021-12-15 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103738 --- Comment #2 from Niklas Haas --- Created attachment 52010 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52010&action=edit No deprecation warning produced

[Bug c/103738] No warning when setting deprecated fields using designated initializers

2021-12-15 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103738 Niklas Haas changed: What|Removed |Added Attachment #52009|no_warning.c|warning.c filename|

[Bug c/103738] New: No warning when setting deprecated fields using designated initializers

2021-12-15 Thread gcc at haasn dot dev via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103738 Bug ID: 103738 Summary: No warning when setting deprecated fields using designated initializers Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: norm