https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
--- Comment #1 from Imple Lee ---
This is probably a regression.
GCC 13.2 can generate optimal code.
See https://godbolt.org/z/4n8ovr7jr .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
Matthias Kretz (Vir) changed:
What|Removed |Added
CC||mkretz at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
K
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
--- Comment #4 from Matthias Kretz (Vir) ---
I'm fairly sure it's not the same source anymore. I'll try to understand where
it goes wrong in the library, because the vector_t{0, data[0], data[1],
data[2]} expression is still optimized as expecte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
--- Comment #5 from Hongtao Liu ---
I saw pass_eras optimize BIT_FIELD_REF of big memory into load from small
memory
Created a replacement for D.161366 offset: 0, size: 64: SR.20D.170101
Created a replacement for D.161366 offset: 64, size: 64:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
--- Comment #6 from rguenther at suse dot de ---
On Wed, 17 Jul 2024, liuhongt at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
>
> --- Comment #5 from Hongtao Liu ---
> I saw pass_eras optimize BIT_FIELD_REF of
