https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097
--- Comment #7 from Fabio Cannizzo ---
Apologies for my ignorance. Thank you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097
--- Comment #3 from Fabio Cannizzo ---
Hi Richard
Using -fno-strict-aliasing the issue disappear, however I am not sure if that
is a real fix, or if it is merely circumstantial.
As mentioned, there are many other possible workarounds which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097
--- Comment #1 from Fabio Cannizzo ---
Changing the `#if 1` to `#if 0` is probably the easiest way to isolate the
debug. It causes only minimal changes to the generated assembler.
I forgot to mention, the code is compiled with the flags
-O3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097
Bug ID: 111097
Summary: mistifying bug triggered by trivial code change
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110202
--- Comment #5 from Fabio Cannizzo ---
> Well, there is nothing magic on exactly 0x55 immediate, there are 256
> possible immediates, most of them use all of A, B, C, some of them use just
> A, B, others just B, C, others just A, C, others just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110202
Bug ID: 110202
Summary: _mm512_ternarylogic_epi64 generates unnecessary
operations
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal