[Bug target/111698] Narrow memory access of compare to byte width

2023-10-25 Thread ubizjak at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111698 Uroš Bizjak changed: What|Removed |Added Target|x86_64-*-* |x86-*-* Target Milestone|---

[Bug target/111698] Narrow memory access of compare to byte width

2023-10-25 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111698 --- Comment #4 from CVS Commits --- The master branch has been updated by Uros Bizjak : https://gcc.gnu.org/g:678e6c328c77db383431751bcfcf867b02369bd6 commit r14-4928-g678e6c328c77db383431751bcfcf867b02369bd6 Author: Uros Bizjak Date: Wed O

[Bug target/111698] Narrow memory access of compare to byte width

2023-10-24 Thread ubizjak at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111698 Uroš Bizjak changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at

[Bug target/111698] Narrow memory access of compare to byte width

2023-10-05 Thread ubizjak at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111698 --- Comment #2 from Uroš Bizjak --- (In reply to Richard Biener from comment #1) > I guess we could do this even on GIMPLE and in general to aligned sub-word > accesses (where byte accesses are always aligned). > > It might be also a good fit f

[Bug target/111698] Narrow memory access of compare to byte width

2023-10-05 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111698 Richard Biener changed: What|Removed |Added Target||x86_64-*-* Keywords|